CoffeeScript 2.0 Beta Released
coffeescript.org
CoffeeScript 2.0 Beta Released
1–9 of 9 posts
Re: CoffeeScript 2.0 Beta Released
#2AFAICT, the only reason it's a point release are the breaking changes. Unfortunately, in order to stay relevant, coffeescript needs a major overhaul, though I must add that its biggest problem (the readability of tab denoted closures) is probably one that needs to be ultimately solved by the IDEs.
Re: CoffeeScript 2.0 Beta Released
#3Sadly, this is rather underwhelming. AFAICT, the only reason it's a point release are the breaking changes. Unfortunately, in order to stay relevant, coffeescript needs a major overhaul, though I must add that its biggest problem (the readability of tab denoted closures) is probably one that needs to be ultimately solved by the IDEs.
Re: CoffeeScript 2.0 Beta Released
#4Re: CoffeeScript 2.0 Beta Released
#5Sadly, this is rather underwhelming. AFAICT, the only reason it's a point release are the breaking changes. Unfortunately, in order to stay relevant, coffeescript needs a major overhaul, though I must add that its biggest problem (the readability of tab denoted closures) is probably one that needs to be ultimately solved by the IDEs.
Does anyone still use CoffeeScript? I guess legacy projects, but new projects can use es6 + Babel or Typescript and get most (if not all?) of CoffeeScript's functionality.
CoffeeScript’s intent, however, was never to be a superset of JavaScript. One of the guiding principles of CoffeeScript has been simplicity: not just removing JavaScript’s “bad parts,” but providing a cleaner, terser syntax that uses less punctuation and enforces indentation, to make code easier to read and reason about. Increased clarity leads to increased quality, and fewer bugs. This benefit of CoffeeScript remains, even in an ES2015+ world.
so, it's not really about "CoffeeScript's functionality" but more it's "style".
Re: CoffeeScript 2.0 Beta Released
#6Sadly, this is rather underwhelming. AFAICT, the only reason it's a point release are the breaking changes. Unfortunately, in order to stay relevant, coffeescript needs a major overhaul, though I must add that its biggest problem (the readability of tab denoted closures) is probably one that needs to be ultimately solved by the IDEs.
Does anyone still use CoffeeScript? I guess legacy projects, but new projects can use es6 + Babel or Typescript and get most (if not all?) of CoffeeScript's functionality.
Re: CoffeeScript 2.0 Beta Released
#7Sadly, this is rather underwhelming. AFAICT, the only reason it's a point release are the breaking changes. Unfortunately, in order to stay relevant, coffeescript needs a major overhaul, though I must add that its biggest problem (the readability of tab denoted closures) is probably one that needs to be ultimately solved by the IDEs.
Does anyone still use CoffeeScript? I guess legacy projects, but new projects can use es6 + Babel or Typescript and get most (if not all?) of CoffeeScript's functionality.
Re: CoffeeScript 2.0 Beta Released
#8Earlier quoted context omitted.
Does anyone still use CoffeeScript? I guess legacy projects, but new projects can use es6 + Babel or Typescript and get most (if not all?) of CoffeeScript's functionality.
from the link: CoffeeScript’s intent, however, was never to be a superset of JavaScript. One of the guiding principles of CoffeeScript has been simplicity: not just removing JavaScript’s “bad parts,” but providing a cleaner, terser syntax that uses less punctuation and enforces indentation, to make code easier to read and reason about. Increased clarity leads to increased quality, and fewer bugs. This benefit of Coff…
Re: CoffeeScript 2.0 Beta Released
#9Earlier quoted context omitted.
Does anyone still use CoffeeScript? I guess legacy projects, but new projects can use es6 + Babel or Typescript and get most (if not all?) of CoffeeScript's functionality.
from the link: CoffeeScript’s intent, however, was never to be a superset of JavaScript. One of the guiding principles of CoffeeScript has been simplicity: not just removing JavaScript’s “bad parts,” but providing a cleaner, terser syntax that uses less punctuation and enforces indentation, to make code easier to read and reason about. Increased clarity leads to increased quality, and fewer bugs. This benefit of Coff…