Mon 06 March 2017 by A Silent Llama
I have, quite unintentionally, become a web programmer. I never wanted to be. I’ve always preferred doing systems programming - especially system stuff that does not involve GUIs. However there are some distinct advantages to building systems available via a browser - things like deployment, upgrades and availability - and since I work in a small development team I guess it was inevitable.
Well - for some reason I’ve never clicked with Scala. It seems to be one of those languages I should really like but we keep missing each other. I can’t even give a good reason for it. Similar for Coffeescript - I tried it out but we never became friends (and it’s basically died out - looks like no one uses it anymore).
As far as Elm goes it looks fantastic but I had some trouble getting going with it - the tooling doesn’t seem to be good enough yet. It makes me think of clojurescript actually - when I first tried clojurescript I dropped it because it didn’t seem to be mature enough. So I’ll review Elm again in a while. (Edit: I’ve managed to get everything working now with Elm - looked like I was having issues with an older npm install. I like the design a lot and will definitely review at some point).
There are probably lots of other options. The thing is Clojurescript circa 2017 is a very different animal to the one I first saw back in… 2012 was it? The tooling works. I don’t need to fiddle for hours to track down some strange dependency or mismatched Java version or whatever. You can create a project and be productive in minutes (seconds even). The library eco-system is flourishing. There are some remarkable technologies that Clojurescript has now that makes it a compelling option (Reagent and core.async being two that immediately come to mind).