Hacker News new | comments | show | ask | jobs | submit login

I'll keep on using JavaScript.



I hope you came to this conclusion by actually trying out the language.

I have written thousands of lines of coffeescript and I have never faced the mentioned problems.

Besides, you can always use the pragmatic approach and use parenthesis in case of ambiguity.


I work in teams scattered across the globe with different experience levels, so we all tend to avoid fashion languages.

On top of that, experience shows that transpiling to JavaScript increases the debugging overhead as now besides debugging our own code, we need to debug what the Transpiler has generated.

Source-maps won't cut it, because they are not available in all browsers we usually are required to support.


Check out Dart. It has less problems than JavaScript, not more.


Let me know when it is supported natively in all browsers.

The teams I work with won't use any language that translates code into JavaScript.


I assumed your comment would be related to the article, my bad.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: