Don’t know about tailwind but I used styled-components and not going back to vanilla css. CSS seems to be designed to be used with HTML, which did make sense back when it was created. Modern web is 99% JS and components composition which does not work well with Vanilla CSS in terms of class name uniqueness, specificity. Also it easy to dumb shit with CSS, like, I worked in the project where we had a lot of legacy global CSS. We had like dozen CSS styles which were adding margin to , and so on. I mean no classes, just globally. I’ve been forced to add ‘all: unset’ to basically all my new components just to avoid changing global styles and breaking something else. Do not recommend.

Nope, JS is “You think you are nerd”.

Also, why React is there? It’s a lib not a language

While trade war isn’t good for anyone US is clear looser here since China’s export to US (as of 2023 stats) is only 15% from its overall export. They can sell more other countries to smoothen impact. Meanwhile who gonna buy US stuff? “Best friend“ Russia with total GPD of less than California?

I feel like people are complaining about wrong thing. At least for me it’s not a problem that there are different communities. To me problem is same posts. What would be great is to have same posts merged into one post with comments from all its duplicates. This way communities are independent, lemmings don’t get to scroll same copy-pasta and discussion of same thing is visible cross communities/instances. Question is how we define “same” is it carbon copy of post, or same content only? Alternative titles can be shown if content is same but not title.

And this is how your city’s traffic, pollution, petrol expenses, stress, respiratory disease infections go up coz some CEO feels power forcing others to do something unnecessary just because they can

What you expecting called natural sorting. Mac employed natural sorting back in 90s. What you get is legitimate Alphabetical sorting which used by Linux and Windows. Natural sorting parses tokens in the string and compares them. Alphabetical sorting compares two strings by comparing individual characters at same index (position). Alphabetical sorting is quite common as it simpler to implement (or rather harder to screw up) and yields predictable results

One of many libraries for Python which implements natural sorting https://github.com/SethMMorton/natsort

95% exaggeration. Here is reality:

• yeah you need main class coz it’s OO-language. Though, not required anymore, which should’ve been done once Java got scrip language capabilities (jshell) back in JDK 9. But as of today not required anymore
• imports exist in most if not all languages. Gotta be insane writing them manually in 2010 let alone 2024
• installing Java runtime (JRE) is as simple as installing any app. Though for installing JDK you need 5 mins for setting PATH. Think about JDK as like TSC or Webpack and JRE as a Browser. I’d argue installing and configuring JDK is simpler than TSC or Webpack
• Unless you doing some non-trivial multi-threading your stack trace will tell you exactly where is your NPE. You gotta be as blind as my teammates to spend more than 1 minutes to find where it is coz it literally tells you file and line numer where Exception occurred
• I mean, yeah if you use IDE from 2000 it will look like it. IntelliJ looks modern, though I don’t like the fact latest versions look like VSCode
• I hardly reach 3G of deps from all 10 projects I have on my workstation.
• IDK what anon means by ecosystem here, Java ecosystem is quite standard across the board. JDK(std lib), Maven/Gradle(deps, build, publishing), Spring Framework (all sorts of blueprints and solutions to standard app level problems), Hibernate/JPA (ORM), JUnit+Mockito (testing). These are tools and libs used in 90% of projects I worked on. Of course there will be more depending on project needs. Layers? It’s not like language imposes any layers whatsoever. It’s just common practice to have 3-4 layers and some glue in-between.
• don’t do GUI in Java it sucks and will suck until Java gets string interpolation. Hopefully soon
• concurrency is actually the only thing which is really bloated in Java. Which will change with next LTS version if I remember correctly. And it’s not that hard if you actually read the f manual and not just “try and hope”. Again it will become much more efficient and easier to follow soon. As of now - yeah, not trivial. But people mostly prematurely optimize, so karma
• Java is kinda have 20 ways to do same thing but actually no. Java built with idea of providing simple building blocks. Then it provides more specific API built on top of those building blocks. It allows to have API which solves typical problems and provides capability to solve custom problems with those building blocks. People often confuse this as many ways to do one thing but it’s like saying “I can have byte array why I need string data type”. Those are different levels of abstraction

Edit: typos

Better explain why pedestrian crossings are stretched so much instead of being on shortest trajectory to other side

Coz money?

Please, can you give an example of such code snippets? I’m wondering what people consider reusable in different projects.

weekend = dayOfWeek > 5

Half of it is fragile CEO ego reply