41–50 of 91 posts
Earlier quoted context omitted.
A doom dependent on full adoption of ES6 could easily be a decade out, to be fair. There aren't, as far as I know, any browsers that expose ES6 without non-standard compile/runtime flags, and we have to wait until there's enough adoption that the % of people using pre-ES6 browsers is negligible. Hell, I'm still waiting for Array::map to be dependable.
Hell, I'm still waiting for [1, 2, 3].indexOf(2) to be dependable ;)
Earlier quoted context omitted.
Considering companies like Dropbox and GitHub use it (even outright recommend it), I'd say it's pretty mainstream.
As well as Palantir.
Is coffeescript still hip? I used to read a lot about it on here, maybe a year or two. Where is it at? Mainstream?
Is coffeescript still hip? I used to read a lot about it on here, maybe a year or two. Where is it at? Mainstream?
There has been a development of hate towards CoffeeScript in most JavaScript communities. CoffeeScript seems to be very popular in the non-JS communities that need to write JavaScript, like in the Ruby and Python web development communities. CoffeeScript was designed for non-JS coders to feel a lot more comfortable writing JS.
This is FUD. CoffeeScript is JavaScript, and if you come into CoffeeScript thinking it works like ruby just because it looks like ruby then you're in for a rude awakening.
Personally, I'm a fan of CoffeeScript's streamlined syntax compared to JavaScript.
For example:
describe 'when the universe exists', ->
it 'should be active', ->
expect(universe.active).toBe true
describe('when the universe exists', function(){
it('should be active', function(){
expect(universe.active).toBe(true);
});
});
Is coffeescript still hip? I used to read a lot about it on here, maybe a year or two. Where is it at? Mainstream?
There has been a development of hate towards CoffeeScript in most JavaScript communities. CoffeeScript seems to be very popular in the non-JS communities that need to write JavaScript, like in the Ruby and Python web development communities. CoffeeScript was designed for non-JS coders to feel a lot more comfortable writing JS.
There's also a nice writeup of some of the more user-visible changes available here: https://gist.github.com/aseemk/8637896
>When requiring CoffeeScript files in Node you must now explicitly register the compiler. This can be done with require 'coffee-script/register' or CoffeeScript.register(). Also for configuration such as Mocha's, use coffee-script/register.
Since I have not been specifying my CoffeeScript version, I have a feeling this update is going to break a lot of my Node.js code. Am I right?