News for hackers. Stuff that matters.
Re:Storm 2.0 by pvorb on Sunday June 02, 2019 @06:05PM (#20078600)
The compiler is significantly slower than Java's, though.
Re:Storm 2.0 by vbezhenar on Monday June 03, 2019 @08:07AM (#20082280)
That's the sad truth for a lot of modern compiled languages (I think Go is an exception). While I did not dig into their compiler internals, it just seems an inevitable consequence from a powerful language (Go is pretty simple in that regard). C++, Rust, Scala, Kotlin, Swift, they all have significantly longer compilation times compared to their predecessors. Probably that's the price we have to pay.
Re:Storm 2.0 by bjoli on Tuesday June 04, 2019 @04:25PM (#20098871)
Chez compiles a 80Kloc project of mine in less than a second, and apparently that is still 2x slower than before they switched to a nanopass compiler.

There is no reason compiling things should not compile at similar speeds to chez unless you are telling your compiler to ootimise everything.

C++/ruae are just exceptionally slow and it became the new bottom line somehow. I know rust does a lot of housekeeping, but after using chez and sbcl, 45s for a 1.5kloc project is killing me inside.

Re:Storm 2.0 by pjmlp on Monday June 03, 2019 @10:05AM (#20083159)
Not really.

.NET Native, D, Delphi, Ada and Eiffel also have pretty fast compilers, while offering quite powerful languages.

Lets even pick Turbo Pascal 7.0 for MS-DOS, which was quite feature rich, and was able to compile very large programs in a couple of seconds.

Also Visual C++ with modules preview support, incremental compilation and linking is also reasonably faster than the FOSS alternatives.

It is only a matter how much money one is willing to invest into improving tooling support.

Re:Storm 2.0 by cryptos on Tuesday June 04, 2019 @05:01AM (#20093236)
As far as I know Google is supporting JetBrains in making the Kotlin compiler faster.