3 ms·
The thing with Java - and by extension Scala - compared to Go is that Loom adds yet another concurrency and language mechanism - so developers have yet another
by Cthulhu_ 5y ago
The thing with Java - and by extension Scala - compared to Go is that Loom adds yet another concurrency and language mechanism - so developers have yet another thing to decide and choose from, and a risk of mixing styles together.
Whereas in Go there's only one way and that's it. pretty much. Oversimplified maybe, but my point is, 'bigger' languages offer options, and options increase overhead.
I support having simplified subsets of languages - or rules in a company, whatever - that sets standards as to which language, stdlib and library features to use. Less options reduces complexity. At the cost of code volume maybe, but code volume is not and never has been the problem - complexity is.
- solaxun 5y agoI think the idea with Loom is that you won't have to deal with the red/blue pill bifurcation of sync/async code anymore. It's a return to basics where everything is once again a thread and can be written synchronously, with the runtime handling the scheduling of the userspace threads. In theory this would be very similar to what Go offers, in practice I guess we'll see once it's released, whenver that is.
- eweise 5y agoLoom is just lightweight threads so you don't have to use third party async libraries to get better performance.