This year, Clojure cemented itself as my favorite programming language, and I felt glad to be able to use it daily for my work, as it does take so much effort off the developer for little things, allowing one to concentrate more on big things.
However, it was also the year I learned that, while Clojure, as a dynamic typed language running on a VM, is the best of that class of languages, static system languages are still irreplaceable for so many other things. This was the year I realized that one language does not fit all, and that it is okay to have more than one favorite language. (And in my case, it is Clojure and C++ that I am now using equally, and with equal enjoyment, and for entirely different reasons).
Clojure is one of the most addictive languages I've ever worked in. I can see why so many people pick it up as something to build hobby projects with, it's just so damn fun to write.
Ideally, you wouldn't be restarting the process all that often. I'll typically be REPL'd in for quite a few hours at a time as I'm developing (only reason for restarts is usually pulling in new dependencies, or if your state gets out of whack; which is something that doesn't happen all that often after adopting Stuart's "reloaded" workflow based on component)
I can't speak for other people, but I guess being a person and considering switching from Clojure because the development workflow has a long feedback cycle that the answer to your question is a yes?
I have Ring reloading code for me as it changes, however if there is a syntax error or exception in a thread, code doesn't get reloaded and strangeness ensues, requiring me to kill the jvm instance and start it up again. Stuart Sierra talks about this problem in his reloaded workflow, and how it's still a problem for him, but he at least now has a faster way of refreshing his app instances.
The REPL takes a bit to start, and then I leave it running for days. The startup time really has nothing to do with the development experience once you're in the system. Even very large projects compile in less than a second for me.
I agree. I've noticed that programmers are often evangelical about their favorite language, and it gets tiring sometimes to say "yeah, but..." Sometimes, you just need a different tool, and efforts to make one language do absolutely everything well are not usually the best way to spend one's time.
Clojure is not really an option when you do systems programming, such as writing native apps, command line tools, working on small devices like a Pi, etc. There are many things I'm exploring in C++ for which Clojure is just not a good tool for the job.
But also, there are some really great C++ libraries in the areas of physics and graphics, and there is no equivalent of the in Java I could use.
There are a few Clojure-inspired Lisps that are meant to be suitable for writing command line apps. I'm trying to work on one myself in fact (https://github.com/sdegutis/Paladin), with the main goal being that it's written entirely in C and has 0 (required) external dependencies -- both goals having been inspired by the implementation and design of Lua. But I'm no expert at implementing languages so it's coming along slowly.
Some days I wish I hadn't completely scrapped and deleted my Mac-only Clojure-only native IDE. It was fricken cool, even if it wasn't Emacs. I think that thing had promise. Welp.
Oh wait, you didn't find it, you're the one who forked it! I should pay closer attention to usernames heh. Thanks so much for forking it and holding onto it for this long. Out of curiosity, if you did have the time, what kind of things would you have hacked into it?
Probably once a year, I go through my Github projects and delete ones that have absolutely 0% interest, including from myself. I would have used my IDE (Leviathan) myself but it's hard to compete with Emacs. With a bit of community help I think it could have become something really cool.
Apparently someone found a fork of it on Github! I've forked it again myself and will keep it for the time being... 575 commits is a lot of time to throw away completely, I shouldn't have been so rash the first time.
Haha. Yeah. There was 0 interest in this app from anyone besides myself, and it was a bit discouraging, so I just felt like "what's the point in making good commit messages anymore?" and had a bit of fun with that :)
However, it was also the year I learned that, while Clojure, as a dynamic typed language running on a VM, is the best of that class of languages, static system languages are still irreplaceable for so many other things. This was the year I realized that one language does not fit all, and that it is okay to have more than one favorite language. (And in my case, it is Clojure and C++ that I am now using equally, and with equal enjoyment, and for entirely different reasons).