Live data from Hacker News

Announcing CoffeeScript 2

coffeescript.org

151–160 of 220 posts

Re: Announcing CoffeeScript 2

#151
post #134
post #10

I can't imagine CoffeeScript will see much adoption these days as most people seem to think ES6+ is "good enough". I miss how concise functions are in CoffeeScript and also miss being able to do object literals without the braces. But there's no chance at all in convincing my team to adopt it, as modern JS really is "good enough".

I honestly think both ES6, Coffee and the like are going in the absolute wrong direction. Every release replaces more keywords with punctuation marks. That's the reason the community abandoned Perl. How much productivity do I gain by replacing "function()" with "() =>"? Round and round we go. Before anyone tells me, yes I know the semantics are slightly different, but muddling the semantics with arcane syntax is not…

>> Every release replaces more keywords with punctuation marks.

I can't think of any other examples. Closures get used heavily in JS and arrow functions do make their use quicker and more concise, as well as fixing `this`. Compared to other languages like Scala, OCaml, Elm and Haskell, with symbols for functional combination and pipelining, pattern matching, and whatever you call the thing where you can miss out parameters and use underscores in function bodies in Scala ... JS is relatively light on symbols.

Re: Announcing CoffeeScript 2

#152

This is honestly the first time I have looked close at CoffeeScript. At a passing glance, it looks really close to Python with javascript elements added in. Is that a correct assessment? If it is, this might be for me. My other question is: how nice does coffee script play with other libraries? We (unfortunately) use jQuery a lot. I have also been using underscore and lodash as well. Are those two even needed when wr…

If you like Python, you will love CoffeeScript. :) I have not used Underscore/Lodash in production, but I use jQuery a lot with CoffeeScript. CoffeeScript does not replace jQuery, although it can make your jQuery a lot nicer. As far as other libraries, there really are no restrictions; CoffeeScript compiles transparently to JavaScript. The only thing holding it back would be poor support in the specific ecosystem you…

[deleted]

Re: Announcing CoffeeScript 2

#154
post #68

CoffeeScript is still very relevant for me. I have two medium-sized Ember projects written in CoffeeScript (and Emblem and Sass--the original, indented variety, thank you very much). I have been looking at React (will probably skip due to the patent license) and Vue, but cannot imagine going back to semicolons and (excessive) curly braces and parens. If you married CoffeeScript just out of convenience (being able to…

i also don't use CoffeeScript because of any 'feature' it has over standard JS but instead because of its concise but expressive syntax. it's less about what it does have/do, and more about what it doesn't have/do. some small aspects of CS i forgo because they (in my opinion) are a little too concise such that they sacrifice readability, but all in all it has my favorite syntax of any language.

CS breaks the ternary ?: operator which is a big headache for me.

Re: Announcing CoffeeScript 2

#155
post #88

Augh. Anytime I see a Coffescript project all I see is wasted money trying to recruit engineers who actually want to use it. 90% of people who write JavaScript roll their eyes and move on.

I think most competent js devs would have no problem switching to that syntax. After all CS is just JS.

Re: Announcing CoffeeScript 2

#156
I love coffeescript, I don't find anything else in Javascript that reflects the strict spacing of python and also shorten the code in a pleasantly communicative way.

Re: Announcing CoffeeScript 2

#157

CoffeeScript is still very relevant for me. I have two medium-sized Ember projects written in CoffeeScript (and Emblem and Sass--the original, indented variety, thank you very much). I have been looking at React (will probably skip due to the patent license) and Vue, but cannot imagine going back to semicolons and (excessive) curly braces and parens. If you married CoffeeScript just out of convenience (being able to…

I feel very much the same. My first language is Ruby and CS just clicked.

I continue using it in my Vue projects and it's a pleasure.

I appreciate the work the team has put into bringing elegance and brevity to my daily life.

Re: Announcing CoffeeScript 2

#158

Earlier quoted context omitted.

I loved CoffeeScript, but I felt it was a double edged sword. I would still use it though, if there were JSX style xml/html tags. But React changed everything for me and as a full stack dev, I can use only few frameworks on one level. Edit: Ok, JSX is now supported. http://coffeescript.org/v2/#jsx And I'm glad they broke the different behaviour of =>. It might need a fix in a lot of code bases, but this price is chea…

I'm not a big fan of the new =>, it means the arguments variable will have parent scope in => but not in ->, it kind of erodes into coffeescript's elegance/consistency imho, unless I'm missing something ?

I never used => but when JavaScript introduced the fat arrow and made it different from the fat arrow in CoffeeScript, this introduced a mental barrier for me. By definition, the JavaScript fat arrow is the important one to know.

Re: Announcing CoffeeScript 2

#159

CoffeeScript is still very relevant for me. I have two medium-sized Ember projects written in CoffeeScript (and Emblem and Sass--the original, indented variety, thank you very much). I have been looking at React (will probably skip due to the patent license) and Vue, but cannot imagine going back to semicolons and (excessive) curly braces and parens. If you married CoffeeScript just out of convenience (being able to…

It's easier when you use something like Prettier which formats the code for you, same workflow as coffeescript except less work and possibly more readability.

Re: Announcing CoffeeScript 2

#160
post #67

Earlier quoted context omitted.

I admit it is a funny forum to ask this, but, hey, here we are. Thanks for the response. It seems your situation was unique, and you're definitely fortunate to have a department willing to make this agreement. The Average Joe more than likely can't pull this off, especially if the company can hire a replacement.

actually I don't think it so uncommon. when you travel you meet a lot of people who just quit and can prop. go back to the job when / if they return. just do it.

This isn't recommended. If you quit the company, that shows you obviously do not want to work for them.

If you quit once, what's the likelihood you'll quit again? And how soon? Why waste everyone's time? You'll need to make a seriously good case as to why the company should rehire you.

In Jeremy's case, he wrote a lot of code that a lot of people use around the globe. That adds a lot of value to him. Luckily, for him, the NYT is lenient to bring him back on the job.

Some other companies aren't so nice.

Post reply on HN