CoffeeScript compiles down to ES3, which means it's compatible with Old IE. The ES6 compilers can only compile down to ES5.
Replace CoffeeScript with ES6
71–80 of 178 posts
Re: Replace CoffeeScript with ES6
#72The reason that I like CoffeeScript is that it removes, what I consider, the unnecessary boilerplate of JavaScript and replaces it with a shorthand equivalent and good conventions. I feel that CoffeeScript is better at representing the intent of JS than JS. I can visually sift through CoffeeScript and understand the code much quicker than normal JavaScript, which in my opinion leads to more maintainable code. I'm not…
If you've got any sort of programming skill your js will only be concatenated on test and production builds, not on development.
Your last paragraph makes little sense as you should never, ever be debugging a problem on live and I think minification has caused me a problem like twice in the 8 years since it's been popular. And it was pretty obvious when it did as the is wasn't even compiling.
Re: Replace CoffeeScript with ES6
#73Coffeescript is pretty damn ugly. For god sakes can people please use parenthesis when calling functions with arguments?
I do it in my coffeescript for function calls. You just need some guidelines and some discipline.
Re: Replace CoffeeScript with ES6
#74The reason that I like CoffeeScript is that it removes, what I consider, the unnecessary boilerplate of JavaScript and replaces it with a shorthand equivalent and good conventions. I feel that CoffeeScript is better at representing the intent of JS than JS. I can visually sift through CoffeeScript and understand the code much quicker than normal JavaScript, which in my opinion leads to more maintainable code. I'm not…
If you've got any sort of programming skill your js will only be concatenated on test and production builds, not on development. Your last paragraph makes little sense as you should never, ever be debugging a problem on live and I think minification has caused me a problem like twice in the 8 years since it's been popular. And it was pretty obvious when it did as the is wasn't even compiling.
> you should never, ever be debugging a problem on live
Until you have to
Re: Replace CoffeeScript with ES6
#75I give credit to CoffeeScript with really helping to push the ES specs forward and think it helped introduce more people to JS and grow the ecosystem. Heck, I used it for a year, liked it, and had it change some of my approaches to writing JS. That said, I hope it slowly fades into the background as more people go back to vanilla ES6 or go with something more powerful such as TypeScript (or Flux). With the progress a…
I sure hope you're wrong. The unnecessary clutter of plain JS is just painful to look at. I can't remember how many times I've looked over a 40 line block of JS searching for a missing. When there are many )} )}; } ; } ; } -- it is just downright frustrating to be be wasting any time on what is effectively irrelevant syntax. With CS, it's indent and be done with it. It's like SASS vs. SCSS. Or Haml vs. ERB. I can't,…
Ditching all the useless lines of closing brackets and parenthesis is my favorite part of using coffeescript. Matching up brackets is a pain. The less I have to do that, the better.
Re: Replace CoffeeScript with ES6
#76First time I heard of sprockets (weird, being German). How many JS build tools are there out now? And is none of it deprecated/abandoned?
Other than that, the braces/indentation issue alone will keep people with CS. Can its compiler emit ES6, by the way?
Re: Replace CoffeeScript with ES6
#77Re: Replace CoffeeScript with ES6
#78it solves a lot of the problems that CoffeeScript is trying to solve without drastic syntax changes. I cannot speak to authorial intent, but for me the majority of the problems CoffeeScript(and moreso LiveScript) solves are syntax ones.
Same, if I squint a little I'm just writing Python that runs in the browser.
Re: Replace CoffeeScript with ES6
#79Earlier quoted context omitted.
Semicolons are already optional in JS. Automatic semi colon insertion (ASI) has a clear set of rules that are pretty easy to remember. http://mattdesl.svbtle.com/to-semicolon-or-not
But ASI is controversial, because of the bugs that can be caused by it. (See "JavaScript, the Good Parts"). I make our devs (myself include) use semicolons with jshint, because I believe it's too easy to screw up.
After reading the linked [Isaacs](http://blog.izs.me/post/2353458699/an-open-letter-to-javascr...) post it made me realise a bit more about the language. I don't think I'd agree its easy to screw up. Its as easy as accidentally using global variables.
Re: Replace CoffeeScript with ES6
#80First time I heard of sprockets (weird, being German). How many JS build tools are there out now? And is none of it deprecated/abandoned? Other than that, the braces/indentation issue alone will keep people with CS. Can its compiler emit ES6, by the way?
Sprockets is part of the Rails asset pipeline - it's not used much outside of the Rails world.