News for hackers. Stuff that matters.

A comment on Treating JavaScript like a 30 year old language. Parent comment

Re:Treating JavaScript like a 30 year old language by ricardobeat on Wednesday July 04, 2012 @05:12PM (#4200848)
Hi Jeremy. Dmitry's argument you mention, for instance, is questionable and not very popular. I think I can't point to what you're going against (vs "old style" coding), maybe some examples in the post could help.

On CS: you are already using a compile step that dynamically changes code, how more complex can it get? I have thousands of lines of CS in production and it never caused any more problems than JS. If you think of CoffeeScript as a tool to write Javascript, not a separate language, things go much smoother (you want to debug the javascript output, not the cs source).

[ Parent | on HN ]
Re:Treating JavaScript like a 30 year old language by jerbils on Thursday July 05, 2012 @10:27AM (#4203140)
Debugging compiled code is absolutely unpleasant. Fortunately, I only have to do it rarely. From what I can tell, debugging JavaScript that was compiled from CoffeeScript is a standard practice, and I simply don't want to pursue that. It's interesting how you describe CoffeeScript as a tool rather than a language, but in my opinion it is still a very leaky abstraction.

As I mentioned, I look forward to revisiting it when a standard toolset has matured.

[ Parent | on HN ]