this whole article stinks of AI prose, why should i read it

the author loves Erlang, but not to the point of writing their love themself

They explicitly casted it to an 'Int' on the mojo side, but the modular website claims that isnt a specific bit-width so i am surprised

It's not a specific bitwidth in a sense that it maps to whatever largest integer type is natively supported by the target architecture (i.e. basically 32-bit or 64-bit).

What do you want from the ecosystem?

- faster compile times

- faster compile times

- faster compile times

- I want sbt+scalatest (the blessed build tool/test framework) to not leak memory constantly (https://olegych.github.io/blog/sbt-fork.html this is an issue I specifically run into)

- I want useful documentation when I ctrlclick into settingKeys in build.sbt

- I want Intellij to not bug out when you pass explicitly the implicit arguments required by a function that uses both context bounds and implicits

- I want intellij to always agree with the scala compiler

The first five points are fixed by using Mill

https://mill-build.org/mill/comparisons/why-mill.html#_perfo...

I'd like better debugging of async call stacks. Seems that'll start working better, with Java 21 and virtual threads, so looking forward to that.

And support for Scala in [web frameworks for Java].

Still on Scala 2.13, so don't know what 3.* I'd want, more than what already exist

We have to be more specific about this “tooling” - what are you missing

Not sure why this is being downvoted. It's hard to do something actionable based on abstract critique.

Please help bring attention