Making the move from Scala to Go

Re:Making the move from Scala to Go by joshlemer on Tuesday January 24, 2017 @11:00PM (#13478373)

If you run `~` before any command, sbt watches the directory for any source changes, and on detecting source changes, redoes the command. So `sbt ~compile` will re-compile any new sources as soon as they are saved.

[ Parent | on HN ]

Re:Making the move from Scala to Go by jpliska on Wednesday January 25, 2017 @01:24AM (#13479168)

The use of the ~ here illustrates the problem in the scala world: a lot of surprising bells and whistles. Why not call it watch instead of ~?

[ Parent | on HN ]

Re:Making the move from Scala to Go by justinhj on Wednesday January 25, 2017 @09:43AM (#13481697)

Or just use IntelliJ and you can reload classes while your program is running if you want. Sbt is a very powerful tool but it's not written with readability for new users in mind.

[ Parent | on HN ]

Re:Making the move from Scala to Go by Sphax on Wednesday January 25, 2017 @04:22AM (#13479973)

Wait, how does that help build time exactly ? It may help with the perceived build time, but your CI builds are still taking the same (long) time.

[ Parent | on HN ]

Re:Making the move from Scala to Go by floatboth on Wednesday January 25, 2017 @05:25AM (#13480239)

CI, sure, but on dev machines this means you're not throwing away the JVM and restarting it, reloading all the classes etc. on every build

[ Parent | on HN ]