Sadly I think you're right. It's a pity that such a beautiful language doesn't get more love, but the comments I see most all come down to some version of broken or wonky tool chains. It's not the language proper, it's the ecosystem.

Why not go or java?

@@mqtrade5743 The way Scala implements OOP is the latest and most developed way to implement it, if you understand programming language theory very well, you will see what Martin Odersky has delivered is truly a master piece.

19:40 I guess is the answer

Right now, the focus is on providing a very similar API to Python PyTorch, to ease porting models. But it would be great to add an immutable API (i.e. like JAX) as well. Contributions welcome!

You seem to base your opinion on how the adoption is going, just like a sheep follows the group. This arises the question: Are you even able to make your own opinion? No one seem to make sense out of Gradle or SBT. We are developers and we code Scala, Mill is plain Scala that I understand just like I understand any other Scala project. I don't know what command to run? I look at the code or even use IDE auto completion. It's simple and does not require a PhD to freaking build my project.

@@joan38 You seem to be unable to comprehend complete sentences and get easily excited on seeing shiny things, just like a grade one child would do. The comment you replied to is my own opinion, of course. The point here isn’t how good or bad Gradle or SBT is, but how useful Mill is. Having used Mill, I found it slightly more useful than a POS. I do agree on one point though, building with Mill doesn’t require a PhD, or else you wouldn’t be here.

​@@abhijit-sarkar "You seem to be unable to comprehend complete sentences" => Ok let's see: ""Gradle is such garbage" is not really a motivation for a new build tool" => Ok why? "The first release of Gradle was in 2008, while Mill 0.1.0 was released in 2018." => I understand it's new. In what is this measuring "how useful Mill is"? "Most people in the Java ecosystem haven't even heard about Mill, let alone using it." => I understand not many people use it. In what is this measuring "how useful Mill is"? "When it gets used for 15 years, and in projects with millions of LOC, we can talk about how much, if at all, it stinks." => I understand once the 2 previous points (maturity and popularity) are met then we can judge "how useful Mill is"? Are we offsetting the judgment onto others and following them? "There's just not enough data to make any sort of comparisons now." => So in the end you mentioned 0 concrete technical point of comparison in your comment. The judgment is all based on maturity and popularity. How is this a fair judgment of a piece of tech? This comment would work just fine on Gradle against Maven in 2008-2014. It's purely anti innovation and progression to me.

@@joan38 Sorry, I don’t have the time or patience to read your essay, so, thank you for taking the time for whatever you wrote 😀

True, however it's part of the value proposition, to be able to compose big system, with some of the parts that are already defined.

Scala-Native exists and it currently has 4.5k stars on github.

Because Scala is Difficult . May be Billions People Go to Grammar School doesn't mean all are successful.

object project extends mill.Module { def hello = T { println("Hello World") } } Then you run it with: mill project.hello