News for hackers. Stuff that matters.
Re:Is Clojure dying, and what has Ruby got to do with it? by rockmeamedee on Thursday May 25, 2017 @10:15PM (#14421628)
I just finished watching this talk "ClojureScript for Skeptics" (https://www.youtube.com/watch?v=gsffg5xxFQI) that laid out the pros of ClojureScript and completely sold me on trying it out. Weird seeing this article about Clojure dying right after, too.

In this talk I watched, the speaker argues for ClojureScript for SPAs because it has: * an excellent standard library (great functional programming so no need for lodash or other hacks, no issues with things like map(Integer.parse), solid date support, etc) * Go-level easy concurrency * Immutable types built-in for a fast React experience (immutable.js by default) * built-in Google Closure Compiler for optimizing, (also with sourcemaps and devtools) * built-in tree-shaking (only import what you use) from Google Closure Compiler * built-in code-splitting (don't import the code for the settings page on the home page, automatically load it when the user goes there), also from Google Closure Compiler

And the talk is from 2015! So there's probably been even more added I don't know about yet.

Then again, in 2017 I feel like we have an embarrassment of riches of programming languages. I'm already playing around with Elixir (loving it), wanna try out Rust's zero-cost everythings, and have finally finishing learning Haskell on my back burner.

Re:Is Clojure dying, and what has Ruby got to do with it? by joncampbelldev on Tuesday May 30, 2017 @03:49PM (#14447997)
Also super easy hot reloading with figwheel.

Literally just 'lein new figwheel' and you've got a project ready for everything you mentioned with hot reloading ready to go