3 ms·
Maybe this works for server stuff, but if you are doing client-side JS I feel like adding this sort of layering as more trouble than its worth. But when it com
by alttab 13y ago
Maybe this works for server stuff, but if you are doing client-side JS I feel like adding this sort of layering as more trouble than its worth.
But when it comes to JS, I'm a minimalist.
- lowboy 13y agoI use js compilation (CoffeeScript, Browserify, React JSX, etc) and it is definitely worth the extra layer. I have a setup with Gulp[0] that watches my files for changes, compiles, and then LiveReload[1] automatically refreshes my browser window, so I never have to leave my editor for non-interactive changes. CoffeeScript compilation with gulp-coffee is usually on the order of a few hundred ms, and I'd expect SweetJS to be the same. [0]: http://gulpjs.com http://gulpjs.com [1]: http://livereload.com/ http://livereload.com/ (I use free, OSS command line versions, not the paid OS X app)