Good article from @firstname.lastname@example.org about why #clojure sucks
But @email@example.com recommended it so I'm going to give it a try
@yisraeldov my team regularly hires coop students, and pretty much all of them get productive within a couple of weeks of using Clojure. So, I'm not really buying this Clojure is hard to learn business to be honest.
In Canada, universities have coop programs where students can get 4-8 month work placements while doing their degree. My team's been hiring students to work on our projects for 4 month terms. And we teach them FP and Clojure when we hire them.
@yisraeldov @xahlee You can write hard-to-read code in literally every language out there. It's not the job of the language, but rather that of the developer to write clear and readable code. This problem is addressed by using good design practices, code reviews, testing, and documentation.
If anything, I'd argue that Clojure is much easier to read than most languages because the community has settled on a few common patterns that everybody uses.
Meanwhile, I've contributed to numerous Clojure libraries because I'm typically able to open up a project I've never seen before and easily figure out what's going on there.
@xahlee @yisraeldov my work machine is from 2013 and it has no problems with the JVM. For Clojure specifically, you rarely need to restart the app once it's running. I typically have the app running for days on end while I develop it.
I also find it rather amusing that you complain about Clojure syntax being hard and in the next breath advocate for es2015.
i also much prefer clojure syntax than js.
but, if you want to do web dev, js is the name of the game. that's the thing. the reality.
of course, if you are so invested in clojure in server and everything, then clojurescript would be a better choice. Else, js + typescript, or, goto reasonML, elm, elixir, purescript, as these latter are still dedicated on webdev.
@xahlee @yisraeldov my team has been building apps with ClojureScript for years now, and we don't use NPM or any of the Js ecosystem. Everything works great. These are large apps with over 100kloc on the front-end. I co-presented about one of our apps recently if you're interested:
lol. that's even worse.
NEVER, write unit test.
that's from people who dunno how to code, made worse by corp greed wanting to make create easy replacement coder cogwheels.
Use diff lang, yes, like reasonML, elixir, purescript.
and, study proof theory if you want to replace unit test.
As a side note, for server side stuff I find clj works better than cljs overall. It compiles faster, the REPL integration for editors is superior, and you don't have to deal with async for most things.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!