Re:A Case for Clojure and GraphQL: Replacing Django
by cutler on Saturday October 14, 2017 @06:55PM
(#15474772)
I think that's the point. Although Clojure has been adopted by a small cluster of big names it tends to be ignored further down the food chain. Search Indeed.co.uk's API for title:Clojure in London and you'll find 8 jobs compared with 378 for Python. For the UK as a whole it's 19 Clojure to 669 Python.
[ Parent
| on HN ]
Re:A Case for Clojure and GraphQL: Replacing Django
by yogthos on Sunday October 15, 2017 @10:37AM
(#15477267)
Python has been around a lot longer than Clojure though, especially if you count years of it being used in production. Clojure has only started seeing wide use about 5 years ago.
The fact that it's already used successfully at large companies shows that it is an effective language. Most companies that try it end up sticking with it. So, I'm not really seeing a problem here to be honest.
Re:A Case for Clojure and GraphQL: Replacing Django
by cutler on Thursday October 19, 2017 @11:08AM
(#15508544)
Clojure was released 10 years ago with 1.0 officially announced 8 and 1/2 years ago. Clojure adoption has been stagnant for a few years now. 8 jobs in London after 10 years, IMHO, represents a serious adoption problem.
Re:A Case for Clojure and GraphQL: Replacing Django
by yogthos on Sunday October 22, 2017 @09:03AM
(#15526617)
Python was released 26 years ago, and it certainly didn't have the ecosystem or the popularity it has today 16 years ago.
There are certainly more than 8 jobs in London for Clojure. JUXT https://juxt.pro/index.html alone hires more people than that. Maybe you're just looking in the wrong places.