These are chat archives for ensime/ensime-atom
Scala.jsinstead of Coffeescript for the
@mdedetrich My thoughts are: "would be cool". I started out a bit but struck some problems with integrating in a node.js env. Might be solved or a non-issue, dunno: http://stackoverflow.com/questions/31116258/how-to-provide-and-consume-require-js-modules-in-scala-js-and-extending-classes. I think I started some skeletons on doing the types for say atom API: https://github.com/hedefalk/scala-js-atom.
However, I currently don't feel this is something I rationalize spending time on. At least not right now. There are so many features I'd rather implement. The language is not really a big part of the problem right now. It's all about understanding Atom and churning out UI. I'm in no way a coffeescript fan boy, this is the first coffescript I've written. But coffescript is the way of Atom and all examples and API is done in coffescript. Sure It'd be cool to do scala.js or even purescript (haskell-like) instead, but basically feels like a lot of project "setup" and not that much paypack right now.
.ensimefile contains a
java-homeentry (that is correctly set). I’m wondering if ensime-atom should be using this value while launching sbt?