Hacker Read

petermichaux · 2011-06-26 13:26:38

Yes but many of the ideas in CoffeeScript were likely slated for ES.next before CoffeeScript. So it has been working in both directions.

atomical | karma 2465 | avg karma 1.42 · | 2016-12-07 23:22:26+00:00

Is this where CoffeeScript left off? How would you compare it to CoffeeScript?

Charuru | karma 742 | avg karma 1.95 · | 2011-02-14 08:39:12+00:00

What about coffeescript.

jessaustin | karma 25176 | avg karma 1.77 · | 2015-07-06 01:41:51

Yup. It's as if coffeescript was created by one person (and a bunch of great PRs!), while ES6 came out of a committee.

axiak | karma 473 | avg karma 3.67 · | 2011-09-28 02:36:34+00:00

They claim that it's not what others are doing, but coffeescript is doing it, and it's quite possible that ECMAScript will get it in the future.

DanielRibeiro | karma 40139 | avg karma 9.74 · | 2011-11-24 15:24:03+00:00

Nice to see many of CoffeeScript's constructs coming to ECMAScript.

alanh | karma 7392 | avg karma 3.61 · | 2017-07-19 04:41:47+00:00

what a facile interpretation. CoffeeScript offered a large number of meaningful improvements over ES5, not including superficial syntax differences. It _still_ offers truly meaningful niceties that can make code _better_ than the JavaScript equivalent.

elwell | karma 4299 | avg karma 1.76 · | 2014-01-22 02:33:22+00:00

CoffeeScript is in an interesting place.

vortico | karma 5453 | avg karma 3.42 · | 2017-03-07 16:52:17

What are your personal opinions on the future of Coffeescript? It's still being used for Atom, but I've noticed colleagues are finally getting used to ES6 and similar languages and switching to them. I'm still stuck on Coffeescript though for all of my frontend projects. It's too closely aligned to my utopia of a language to try to find anything else (which would surely have a smaller following anyway).

mirekrusin | karma 4612 | avg karma 1.97 · | 2023-03-22 23:46:33

CoffeeScript impacted ECMAScript more than anything else.

elijahmanor | karma 567 | avg karma 4.05 · | 2012-02-08 14:35:31+00:00

Ohh nice, maybe there is where CoffeeScript got inspiration from? The syntax looks very similar.

sandstrom | karma 2456 | avg karma 3.45 · | 2017-09-18 17:11:33

This is true (few adopting coffeescript), but CoffeeScript influenced much of todays ES6+, so it still lives on :)

elwell | karma 4299 | avg karma 1.76 · | 2021-06-08 18:37:27+00:00

It started in 2012. A lot of the finer points of CoffeeScript are in ES6, so that might make less sense now.

keyle | karma 13203 | avg karma 4.54 · | 2011-12-12 10:27:56+00:00

Very interesting indeed. Any alternatives to Coffeescript?

tjwii | karma 14 | avg karma 1.75 · | 2018-01-07 12:34:26+00:00

I think it is quite funny how a tool to turn proper code into the mess that is ESxx can become so popular. I'm still using Coffeescript 2, it's awesome :)

holler | karma 1658 | avg karma 1.75 · | 2020-06-21 14:20:14

wow that’s cool to hear! I read about coffee 2 awhile ago and then heard nothing of it. I used to love coffeescript, arguably more than vanilla js, but forces that be led me to move on.

are you working with a team? if so was it easy to get buy-in?

reply

sjogress | karma | avg karma · | 2017-02-24 05:37:53+00:00

Coffeescript 2 has some breaking changes, most notably classes since it is moving to ES6 classes instead of its own implementation.

I'm with you though, I much prefer Coffeescript syntax over Javascript so I'm really happy to see it coming along.

reply

Osiris | karma 10774 | avg karma 4.5 · | 2017-03-08 00:27:54

I've never written CoffeeScript, but I agree that it had a significant impact on the evolution of the ECMAScript standard. A simple example, arrow functions, lexical scope (const, let), and `this` binding.

411111111111111 | karma 2374 | avg karma 2.05 · | 2022-05-09 23:51:43

coffeescript was created around 2009, so unlikely.

abritinthebay | karma 1846 | avg karma 1.04 · | 2017-06-19 06:31:39+00:00

Oh thank god.

CoffeeScript was an important crutch and stepping stone but we're maybe 2 years past where it has been past it's prime and this will make updating and improving legacy projects a lot easier.

Personally was never a fan of it - it used too many Ruby idioms for my taste and produced noisy code that was a pain to debug (at the time) - but it did spur the development & adoption of other, better, systems (ESNext transpilation, TypeScript, etc)

reply