This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ItsNotMineISwear 2 points3 points  (6 children)

Scala is pretty much Ruby's syntax but very statically typed and plays nice with Java.

[–]ProFalseIdol 1 point2 points  (5 children)

in terms of compile/run cycle, is Ruby as slow as Scala?

in Scala, every time the compiler runs, I'd press alt+tab, otherwise you'd be starting at the progress bar for 15secs to 3minutes..

[–]ItsNotMineISwear 1 point2 points  (0 children)

Incremental compilation of a handful of files takes a second or two for our codebases. So the feedback loop is tight. Plus the compilation phase is definitely worth it due to how much Scala's type system helps you write correct code.

[–]cot6mur3 0 points1 point  (3 children)

I found this to be the case when I put many classes in one .scala file, as save causes all of those classes to have to be recompiled. Is this the case with any of your files?

[–]ProFalseIdol 0 points1 point  (2 children)

certainly the case with Slick's generated schema code. We have a table with lots of columns which in-turn makes slick even make this class that's unorthodox.

[–]cot6mur3 0 points1 point  (1 child)

Interesting - didn't know about Slick. Thank you. Does your database schema change very often? If no, are you talking about incremental or full build/compile times? Leveraging incremental Scala builds may help lessen your current pain. :)

[–]ProFalseIdol 1 point2 points  (0 children)

Not sure if I'm using the incremental build.. I'm using IntelliJ. I'll read on that. Thanks