4 ms·
I'd add one thing to the list of requirements before it is enterprise-ready: faster compile times.
by saosebastiao 13y ago
I'd add one thing to the list of requirements before it is enterprise-ready: faster compile times.
- lmm 13y agoYou're right, C++ will never be enterprise-ready. (Scala could indeed really do with faster compiles, but I think that's actually less of a problem for enterprises than it is for the agile startup world)
- seanmcdirmid 13y agoA lot of money has been invested in infrastructure to deal with C++ slow compiles and make it more feasible; Google for example has some amazing build reuse and caching tech. There are many other ways of dealing with slow compiles vs. just making compiles go faster; e.g. you could make them more incremental (which is also useful for IDE use).
- lmm 13y agoScala already has some very good incremental compilation tech, built into its IDE support. For day-to-day coding the compile times aren't an issue (though they can become one if you like to e.g. make releases frequently).
- harryh 13y agoThis probably depends on how much code your compiling. For small projects it's not an issue. For larger projects it can be a very very big issue.
- bcbrown 13y agoUgh, ever since we added scala to our projects, the compile-time has doubled. It's certainly an issue to me. It makes it harder to get into flow when I have to wait several minutes for compilation.
- lmm 13y agoFor day-to-day coding where you need that flow you should be using an IDE with incremental compilation. Full compiles are for releases or the like.
- seanmcdirmid 13y agoOnly at the file level, and nothing as advanced as state of the art that google has for C++ (but where people are building the same thing anyways). I did tree level incremental compilation in Scala for the presentation compiler, but Martin replaced that with laziness, which obviously isn't the same thing.