sonicgear1

I can't wait for the downfall of AI. It has become like a plague at this point.

SolidJS is what Svelte5 should have been

From slop to even bigger slop, congrats!

Quarkus beats the crap out of Spring in every possible aspect, perf, DX, you name it.

You should catch any non specific exception in the last catch block, just in case. Thought that was the standard. Java gets very messy in mixing checked and unchecked exceptions, I've seen a lot of devs just ignore the unchecked ones.

We had the same problem. Svelte would have been perfect if it only had a true SPA router. SvelteKit is too complicated for a simple SPA.

Hacker news is just too keen on shitting on .NET In my experience switching from Java to .NET was an epiphany. The language is 10x more concise, async/await is the same as in javascript, the documentation and official guides are miles ahead of Java, and it's just a pleasure to work with.

Anyone trying to justify the usage of React is just suffering from Stockholm Syndrome at this point.

Its is actually sad just looking from a hardware endpoint. A 2016 iPhone 7 has an advanced 5 nanometer CPU. That is really powerful when looking at the grand scheme of things. Yet most react "websites" will completely obliterate it and make the phone get blazingly hot. I do this for fun a lot when browsing the web: when a website makes my phone literally melt, I check its stack on my PC and sure enough it is almost always React paired up with Redux. These performance apologetics are sad.

Agree. Java can't even get the simplest things right. This stuff makes me want to cry.

Please don't follow the author's opinion. RadixUI with its' 50kB tooltip is not something a sane person would use. This is why React websites weight multiple megabytes at times.

jOOQ is not even close to EF LINQ, I worked with both.

Java is just a painful language. At that level of abstraction you would expect to work purely on business logic, yet Java makes you just focus on the boilerplate and lacks completely basic features such as tuples, real generics, async/await, anonymous types and more. Spring is another huge pain point, it's slow and verbose in comparison to Go or even .NET. Java is not even close to Kotlin, that's why it was invented in the first place, to not make you want to shoot yourself in the head. Needless to say, I don't see any real use of Java in 2022 and beyond.