The 2024 StackOverflow survey is out, and for the 8th year in a row, Clojure has ranked near the podium in the Top Paying Technologies category—often occupying rank 1. I don't talk much about why I choose to use a weird Lisp—mostly because nobody cares—but the results speak for themselves. If you can hold your nose long enough to learn something very different, you'll find yourself in a high-productivity environment that features: 🔥 Hot code reloading 🦆 Dynamic typing ♻️ Best-in-class garbage collection 📂 Highly performant immutable data structures 📚 Access to the entire JVM's ecosystem of libraries 🧩 Cross-platform compilation to JavaScript 🧠 An unbelievably smart and humble community Sure, you'll pay a high mental price to learn the language, but as a reward, employers will pay a high price for *you*.
Clojure devs bring a unique perspective to complex problems. High pay isn't just about syntax. It's about value.
I don't understand "Desired vs Admired" and why they replaced "Loved, Dreaded, Wanted" with it.
Consider job availability. High-paying languages like Clojure are great, but having skills in more widely used languages can ensure consistent job opportunities.
I don't see any available Clojure jobs for those outside the US and Western Europe. I know Clojure, but I can't find a Clojure job.
Sooo if we use Go, we can pay our developers the least? Used Clojure for a couple years at a company, I generally found you spent a lot of time debugging Java libraries and dealing with the JVM. My company uses a mix of python and Go. We were all python, then had performance problems (managing large amounts of data and events) with python. We looked at Rust and Go, Go seemed to have the balance of high level and close to other common languages in syntax and ease of use, but Rust was interesting and I could see the low level abilities useful in some applications like if we were creating a new type of database. I also find the language you use should be the one you and your team are most comfortable with. Python got was common in data, we all knew it, and got us a working application with somewhat complex background faster. When we started having specific issues that were known or we could see clearly down the road, we looked at other options and made a decision.
This tells me some companies drank the coolaid and they're still paying for it.
get yer neckbeard lisp outta here!
I'd really love to see a breakdown by country. From what I've seen, most actual, full-time Clojure jobs are based out of the EU. There are a few notable standouts in the US, of course.
Surprising to not see C,C++ in the list.
Product @ Qlik | Data engineer | Advocate for better data
8moIsn't that because there are so few engineers who actually know Erlang, Elixir or Clojure :)