Is it acceptable to use coffeescript in browser using coffeescript.js, or should one always compile it to javascript first? Like... how much of a performance hit am I going to see here?
Name:
Anonymous2013-07-15 7:38
performance
javascript
I would laugh if it was not so sad
I'm well aware that JS is not exactly fast; however, the question is the degree of how much slower it would be to run a coffeescript through coffeescript.js rather than just compiling it.
asm > Fortran > C > C++ > Java > asm.js > JS > CoffeeScript > perl> Python > Ruby > LISP > Shell scripts > Batch files > calculators > mental calculation > writing it down on paper and solving > abacus > counting stones > OG THINK IT TOO HARD > piraha arithmetic
>>4
Not everything has to be done in browser, but any application that has to be run by a large number of clients should be interpreted by that client as much as possible to avoid overworking the server.
The language does not have words for precise numbers, but rather concepts for a small amount and a larger amount.
It's like Nikita whose language doesn't have words for infinity, set, etc.
Are people really taking this bullshit seriously? Native performance my ANUS. You're going to run this shit on a browser called Firefox. Enjoy your memory leaks and bad performance.
Name:
Anonymous2013-07-17 7:21
Why don't they make a virtual machine for Javashit that will be standalone and browser-indepenent? Let the browser only do what it's good at: rendering XML trees with style.