3 ms·
Current stack at work for me is Clojurescript / Reagent / Boot. In JS land, I'm in the React camp. React's model is the biggest step forward on the frontend si
by grayrest 11y ago
Current stack at work for me is Clojurescript / Reagent / Boot.
In JS land, I'm in the React camp. React's model is the biggest step forward on the frontend since jQuery. I stick with React over faster/smaller alternatives (virtual-dom) because the community size network effects mean there's stuff I want to use that I didn't have to write (e.g. React Router). I'm not a fan of any Flux library I've run into (and I've checked a dozen) so I'll be porting my cljs setup whenever I have to switch back. I'm in the functional JS camp so Immutable.js, Ramda, and js-csp for libraries and I run mocha+chai for testing. Keep an eye out for Netflix's Falcor and Facebook's Relay, which are vaporware at the moment but most likely disruptive.
I favor Webpack over the js task runners. It's always mostly done what I wanted and extending it is fairly straightforward. I find the configuration setup somewhat arcane but I've done enough variations that I have a working version of what I want to do somewhere on my hard drive to copy/paste.
Compiler is babel. The dev tools in most browsers are comparable, I'm still mostly on the Chrome ones out of familiarity.