Hacker News Reader

Comment by kylecordes | Hacker News Reader

This sounds snarky, but I mean it earnestly. Rather than move from JS to ClojureScript one library at a time, why not step all at once? I think by the time you use a bunch of libraries this way, you will be almost as far from common JS practice as you would just using CLJS in the first place.

View on HN

I could think of a few reasons why not. Learning curve being a big one. For startups it's the difference in finding developers. Preference could be another, whether you think imperative code to be more readable, or maybe you enjoy classes or other JS-targeting languages.

I've looked into Om/ClojureScript now a few times and the learning curve is steep and keeps putting me off, but also I fear that if I start a project with it I'll alienate potential future devs and have difficulty gaining traction. Plus, with ES6/CoffeeScript/TypeScript and libraries like this it's more possible than ever to build a beautiful environment to code in that doesn't require such a big jump.

But hey, at least this stuff brings more exposure to ClojureScript. That's definitely a good sign.

Clojurescript might be more of a magnet than a filter in finding developers. I think any developer would be excited to learn the language that influenced React and the immutable js libraries... as long as they had some guidance and employment to do it!

In my experience, I joined a company specifically to learn/use clojurescript and others joined the same time, and we were committing code after 2 weeks.

Om has a steep learning curve. I'd recommend quiescent if you want the bare minimum for interfacing with React in cljs.

There is a segment of the JavaScript/Node community that embraces the UNIX small components that do one thing well philosophy. We see all of these things as incremental improvements to be used or not depending on need. Using something like ClosureScript cuts you off from that.

I'm into clojure and clojurescript, but I can see why people would want to avoid the overhead of using a compile to js language. To be honest though, I'm excited about this and all other functional goodies coming to plain JS from om and react (immutable data structure libraries, virtual-dom) because it'll be easier to use them from purescript.

If your company is already using JavaScript and React, it's going to be a whole lot easier to get them to let you use React-cursor than it would be to get them to move over to ClojureScript and Om.

Perhaps when ClojureScript is self hosted. Right now the compile time, project setup, and overall learning curve is a pretty big barrier.

I love Clojure but I do not like Clojure's slow build times.

ClojureScript auto-compiler is really fast (under a second) after the first compile if you don't use advanced optimizations.

ClojureScript auto-compiler doesn't run in my web browser, where I want compilation to happen. Not a shell script I have to manually start every time I want to develop.

Reply on news.ycombinator.com