Live data from Hacker News

CoffeeScript 1.3.0 is out

coffeescript.org

11–20 of 55 posts

Re: CoffeeScript 1.3.0 is out

#11
"CoffeeScript now prints a Generated by CoffeeScript VERSION header at the top of each compiled file."

From what I can tell there's no switch to optionally disable this? I can see how it could be useful to keep unaware developers from making js changes in compiled files, but other than that, what other purpose does this serve?

Re: CoffeeScript 1.3.0 is out

#12
post #11

"CoffeeScript now prints a Generated by CoffeeScript VERSION header at the top of each compiled file." From what I can tell there's no switch to optionally disable this? I can see how it could be useful to keep unaware developers from making js changes in compiled files, but other than that, what other purpose does this serve?

The most important thing it does is tell you which version of CoffeeScript was used to generate the file. Inevitably, as more and more coffee-generated-JavaScript begins to wind up in more places, we don't want to end up in a situation where you have to use trial and error, or distant memory, to figure out which version to use to rebuild the JS.

Re: CoffeeScript 1.3.0 is out

#13

For folks that are curious, we wanted to get these changes out the door -- strict mode syntax errors being a big one -- so that source maps can be the focus of the next release (probably 1.4.0).

source maps can be the focus of the next release (probably 1.4.0)

Source maps in Firefox and Chrome will be one of the most important pieces of software infrastructure since Javascript itself. It will be the realization of Stallman's "one script to unite them all" vision for GNU GUILE from the "Tcl wars." A pity that it isn't Lisp, but there is enough goodness in Javascript (and Coffeescript) to make me very optimistic.

Re: CoffeeScript 1.3.0 is out

#14
Please forgive me for intruding the holyness of CoffeeScript, but I always found and always will find CoffeeScript appaling and unusable. A wrapper for otherwise syntactically and otherwise perfectly readable and codeable JavaScript? Come on guys. Just learn JS, will you?

Re: CoffeeScript 1.3.0 is out

#15

For folks that are curious, we wanted to get these changes out the door -- strict mode syntax errors being a big one -- so that source maps can be the focus of the next release (probably 1.4.0).

Nice source map support will be huge.

Re: CoffeeScript 1.3.0 is out

#17
post #14

Please forgive me for intruding the holyness of CoffeeScript, but I always found and always will find CoffeeScript appaling and unusable. A wrapper for otherwise syntactically and otherwise perfectly readable and codeable JavaScript? Come on guys. Just learn JS, will you?

You're still coding in assembler I assume?

Re: CoffeeScript 1.3.0 is out

#18
post #17
post #14

Please forgive me for intruding the holyness of CoffeeScript, but I always found and always will find CoffeeScript appaling and unusable. A wrapper for otherwise syntactically and otherwise perfectly readable and codeable JavaScript? Come on guys. Just learn JS, will you?

You're still coding in assembler I assume?

Why do that when you already have perfectly readable patterns of bits.

Re: CoffeeScript 1.3.0 is out

#19

For folks that are curious, we wanted to get these changes out the door -- strict mode syntax errors being a big one -- so that source maps can be the focus of the next release (probably 1.4.0).

Regarding source maps... it feels like the solution to the wrong problem. Why are we still pushing minified/obfuscated Javascript to the browser anyway? What's wrong with standardizing on a bytecode format instead (e.g. JVM)?
Post reply on HN