I really liked CoffeeScript, it's a good way to generate sane JavaScript. But I have switched to Elm for larger projects. The maintainability it brings is a lifesaver.
Announcing CoffeeScript 2
111–120 of 220 posts
Re: Announcing CoffeeScript 2
#112This 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 writing coffee script? I'm kind of assuming not, since they're both largely just adding methods/functions.
Re: Announcing CoffeeScript 2
#113This 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…
CoffeeScript is javascript. It is just a nicer (in some people's opinion) form of javascript. It added some much needed features a few years back, but with recent JS advances the utility of coffeescript are much less than they used to be.
So invoking jquery and everything is totally 100% supported. In fact that is how I used coffeescript a few years ago.
Re: Announcing CoffeeScript 2
#114I love CoffeeScript. Thanks for this.
I know, I know, "what about types". Perhaps it'll get there one day. There's always flow.
Thanks again.
Re: Announcing CoffeeScript 2
#115CoffeeScript 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 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 cheaper than having the mental burden of it.
Re: Announcing CoffeeScript 2
#116Earlier quoted context omitted.
> In the end I didn't end up writing anything for them I understand that you didn't write anything professionally about your trip, but did you ever write anything casually about it - blog posts or the like? It sounds like it would make for interesting reading :)
From roughly sketched map to marriage, it's all archived on Instagram. But I'm afraid there's nothing more than that written up ... yet.
I'll check it out and will keep my eyes open. Thanks :)
Re: Announcing CoffeeScript 2
#117This 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 are working with, such as a lack of plugins that automate the build process. In that case, you may need to compile manually or set up your own build script. But other than that, you can use CoffeeScript in place of JS pretty much anywhere.
Re: Announcing CoffeeScript 2
#118Huh, just finished migrating a small 5K front end from CS to Scala.js.
Miss the concision of CS, both in terms of syntax and generated output, but otherwise really enjoying typed JS. Also, it's kind of cool not immediately knowing whether a particular source file is for the front end or back end -- like, oh, wait, this is the front end ;-)
Re: Announcing CoffeeScript 2
#119This 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…
It's "just" Javascript, so it plays quite well with everything. Definitely jQuery. Main issue was that the missing JSX support. It definitely a Pythonic JS, and I much preferred it to JS a few years ago.
Re: Announcing CoffeeScript 2
#120CoffeeScript 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 felt the same way when I switched from CoffeeScript to TypeScript but the type checking was worth all the braces, returns and lack of existential operator. If CoffeeScript added an (optional) type system I'd switch back in an instant.