4 ms·
Java 21 has n:m green threads, but with caveats. Java 24 removed a major source of the caveats.
by cogman10 1y ago
Java 21 has n:m green threads, but with caveats. Java 24 removed a major source of the caveats.
- frollogaston 1y agoYeah, I'm hoping that fixes things eventually. We still can't use that at work, and even once we can, there's 10yo code still using 3 different old ways of async.
- computably 1y agoI'm sure you're already aware but for those who aren't - Java 21 was released in 2023. Golang 1.0 was released in 2012.
- pjmlp 1y agoIn 2012 we could do much of the same stuff with Java 5 concurrency framework and futures (aka promises everyone raves about on JS land), with the advance that scheduling can be customised.
- frollogaston 1y agoThat's what I meant by unreadable code. You have to twist everything to work with whatever async framework.
- pjmlp 1y agoHave you ever had to write down channel sending dependencies graph? I had to, to make sense of whatever was going on.
- frollogaston 1y agoIf this is an app backend, you aren't dealing with Golang channels directly. Your webserver or whatever it is spawns a new goroutine (greenthread) for each incoming request, then you use blocking calls without worrying. Looks similar in JS but the event loop handles it instead, and you async/await stuff. JS webpages and app frontends also don't worry about this. If this is systems programming, yeah you're reasoning about channels, but that's mostly the same in any language. Golang has slightly nicer support for that if anything.