3 ms·

I'm not sure in what way you mean "fight it out", but I'm glad that Heroku opted to start with Clojure... As a guy trying to get on the JVM, the experience of

by icey 15y ago

I'm not sure in what way you mean "fight it out", but I'm glad that Heroku opted to start with Clojure... As a guy trying to get on the JVM, the experience of getting up and running with Clojure has been significantly easier and less "fiddly" than trying to get a decent Scala environment set up.

LiveTheDream 15y ago
Can you explain further what was difficult about getting a Scala environment set up? For me it was "sudo port install scala", "sudu port install sbt", cd to/my/project/path, "sbt".
- icey 15y ago
  Getting Scala & SBT installed hasn't been the tough part, it's getting it working with any IDE that has been complicated. A big part of the problem is that documentation seems to equally point to information for Scala 2.7 and 2.8, and less so for 2.9; but the directions are different for each version. Added to that are the differences between SBT 0.7.x and SBT 0.10.x. It makes it tricky to know what parts of the documentation are still valid and which parts have changed. Then you pick an IDE (Eclipse, IDEA, Emacs w/ Ensime) and figure out what plugins are valid today and what versions of Scala they work with and hope that it all matches up. With Clojure & emacs it's just a couple of commands to get Clojure installed and have a project correctly set up. I do like Scala, but there are still many rough edges that aren't helped by the frenetic pace of breaking changes in the ecosystem. I'm sure part of it is that I'm coming to Scala without any substantive Java background. (For whatever it's worth, emacs with Ensime had the best / most straightforward installation path out of any of the other IDEs)
  - joshhart 15y ago
    In my opinion, working with the IntelliJ has been very easy in Scala. There's an excellent plugin that you may want to check out if you haven't already that lets you generate IntelliJ project files from sbt. https://github.com/mpeltonen/sbt-idea https://github.com/mpeltonen/sbt-idea

by icey 15y ago

LiveTheDream 15y ago

Can you explain further what was difficult about getting a Scala environment set up? For me it was "sudo port install scala", "sudu port install sbt", cd to/my/project/path, "sbt".

icey 15y ago
Getting Scala & SBT installed hasn't been the tough part, it's getting it working with any IDE that has been complicated. A big part of the problem is that documentation seems to equally point to information for Scala 2.7 and 2.8, and less so for 2.9; but the directions are different for each version. Added to that are the differences between SBT 0.7.x and SBT 0.10.x. It makes it tricky to know what parts of the documentation are still valid and which parts have changed. Then you pick an IDE (Eclipse, IDEA, Emacs w/ Ensime) and figure out what plugins are valid today and what versions of Scala they work with and hope that it all matches up. With Clojure & emacs it's just a couple of commands to get Clojure installed and have a project correctly set up. I do like Scala, but there are still many rough edges that aren't helped by the frenetic pace of breaking changes in the ecosystem. I'm sure part of it is that I'm coming to Scala without any substantive Java background. (For whatever it's worth, emacs with Ensime had the best / most straightforward installation path out of any of the other IDEs)
- joshhart 15y ago
  In my opinion, working with the IntelliJ has been very easy in Scala. There's an excellent plugin that you may want to check out if you haven't already that lets you generate IntelliJ project files from sbt. https://github.com/mpeltonen/sbt-idea https://github.com/mpeltonen/sbt-idea