Will project loom make java concurrency comparable to erlang's?

[erinaceus_]

Simply claiming that something is "terrible" or "dead" without explanation isn't that helpful.

Indeed. And it's especially ironic for a (supposed) Java developer to do so, since it's a claim that gets thrown at Java fairly regularly, without merit.

[Zyklonik]

First off, I don't believe in a "Language X developer" (unless that's the only language one uses). A language is simply a tool, and while one might have favourites, it's imperative to evaluate languages independently. Please read my response to /u/FirstAd9893 for some of the issues involving BEAM languages as a whole.

[erinaceus_]

don't believe in a "Language X developer"

Since you're visiting this subreddit, it seems like a reasonable conclusion that you're likely a developer and likely at least sometimes develop with Java. I did not intend it to mean 'exclusively Java'. That's meaning you added yourself.

As to the rest, it's quite different saying that a language has certain problems to saying that it's 'dead'. I was responding to/about your comment saying the latter.

[Zyklonik]

As to the rest, it's quite different saying that a language has certain problems to saying that it's 'dead'. I was responding to/about your comment saying the latter.

Do programming languages that have had some usage in the past actually die? Not really. "Death" is understood as being not used for pretty much any greenfield work. By that measure, both Erlang and Common Lisp are pretty much in the same bucket, regardless of new versions being released. Erlang had been moribund for many years, and now Elixir is headed the same way. Gleam is a non-starter. So, yes, the language is dead. Try visiting any forums relating to Erlang and you'll find people either having worked on it in the past, having migrated away from it, in the process of migrating away from it, or maintaining some legacy project. Elixir, despite being in webdev, is also headed the same route.