Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It is in the top 3 issues with Scala as well. The amount of drag it causes in a project just isn't worth it.


The Rust compiler is much faster than Scala's compiler, from everything I have heard.


really doesn't matter how long the compiler takes, so long as the result is fast.


I want two types of results: when developing, I want fast turnaround and most of the time don’t care about runtime performance; when deploying, I don’t care much about how long it takes to compile, but I want runtime performance to be optimised.


Even if it's a simple idea, IIRC Fabien Bellard suggested to use very simple compilers such as tcc for prototyping and gcc for final built. A few years ago there was also an intermediate step using clang for error messages (and also portability).


That's not true; for quick turnaround it's important to be able to get results out of the compiler quickly.


In what scenario does executable correctness and performance take a backseat to compiler runtime? Seems backwards to me.


There is a reason that every C/C++ compiler has various optimization options. Developers like the compiler to respond quickly to changes and later they'd like the highest performing code at the cost of compile speed.


FWIW, I don't find it to be a big issue in Scala anymore with SBT's incremental compilation.


Depends on how many people are developing on the code base. If every morning is a full build with a few spread throughout the day for integration it is pretty awful. Additionally, I think submit queues are the way to go for committing code to master and if that takes an hour before you know your change is good I'm pretty unhappy. As far as incremental compiles go, just developing in IDEA does a pretty good job.


More than speed it's the ridiculous ram requirements that made me cringe while learning Scala. sbt itself ate 2G of ram on my machine.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: