3 ms·
> I wonder how good the concurrency stuff is these days. What were you missing? Java had threading, task, threadpool capabilities for ages. It comes with all k
by Traubenfuchs 4y ago
> I wonder how good the concurrency stuff is these days.
What were you missing? Java had threading, task, threadpool capabilities for ages. It comes with all kinds of concurrent collection classes and running something in parallel could be just one .parallelStream() away. There are also countless reactive frameworks that minimize thread count. Java Loom / green threads are available since Java 19 (hidden behind a flag).
- endisneigh 4y agoSorry, I meant in terms of developer ergonomics and ease of use, not purely compute performance.
- winrid 4y agoThe Reactive java frameworks are way more developer ergonomic than NodeJS if you use the virtual threads previews, otherwise you have to use callbacks/futures. But at least you have runtime type checking... Vertx is way better than Node in a lot of ways, and faster, and easier to debug. Lock the event loop? You immediately get a log that you did something bad.
- winrid 4y agoLike I just got an error in my IDE with TypeScript "ChartConfiguration is not generic". So I cmd+click into the type definition and it's a ChartConfiguration<T>. okay... The whole ecosystem feels super fragile. It hurts productivity and moral. This just doesn't happen with Java.