The switch: Python to Node.js

Re:The switch: Python to Node.js by sneak on Sunday December 18, 2011 @12:14PM (#3366971)

I think it's amusing that when I claim that javascript is a shitty language, instead of trying to claim that javascript isn't shitty, you point out the shittier attributes of the language I was comparing it to.

Regardless of whether you like python or not, javascript pretty much sucks. Coffeescript helps a bit, but if you aren't running in browser, why hobble yourself like that?

[ Parent | on HN ]

Re:The switch: Python to Node.js by cm127 on Sunday December 18, 2011 @12:50PM (#3367055)

The "Javascript is a shitty language" argument is getting old. I feel like you're only admitting that you're too lazy to learn how to program with a prototype-based language. You even suggest Coffeescript which is big on making Javascript like an OOP language when it's really not.

As far as a reason why you might "hobble" yourself is because Javascript is great at asynchronous design. You should try checking it out for real instead of jumping on the opinion bandwagon.

[ Parent | on HN ]

Re:The switch: Python to Node.js by jashkenas on Sunday December 18, 2011 @03:03PM (#3367349)

Oh man oh man.

    > You even suggest Coffeescript which is big on making
    > Javascript like an OOP language when it's really not.

JavaScript is deeply object-oriented.

[ Parent | on HN ]

Re:The switch: Python to Node.js by rdtsc on Sunday December 18, 2011 @02:20PM (#3367260)

> argument is getting old.

How does the age of the argument impact its validity.

> you're only admitting that you're too lazy to learn how to program with a prototype-based language.

If you don't like Erlang you are just admitting you are too lazy to learn the actor model. See I'll just call you "lazy" it will validate my argument.

> because Javascript is great at asynchronous design.

Not disagreeing with you here, but it would help if you'd actually mention why. You said something about it being a prototype based language. Is that why you think it is great at asynchronous design?

[ Parent | on HN ]

Re:The switch: Python to Node.js by MatthewPhillips on Sunday December 18, 2011 @12:22PM (#3366984)

You expected a nuanced refutation when you yourself offered nothing of substance?

[ Parent | on HN ]

Re:The switch: Python to Node.js by david_a_r_kemp on Sunday December 18, 2011 @02:06PM (#3367223)

At least Javascript isn't having problems with incompatible language versions

[ Parent | on HN ]

Re:The switch: Python to Node.js by Tobu on Monday December 19, 2011 @03:44AM (#3368993)

The language is limited by IE dragging their feet on unbreaking their implementation or advancing standards, Webkit and V8 staying at a very conservative middle ground (Google pushing Dart and compilation as substitutes), and Mozilla being the only engine developer showing willingness to evolve the language, because they are the only ones using it to implement the rest of their browser. Node.js is held back by a language implementation they don't control and feels underpowered in the language department, indirectly being a victim of resistance to change in the browser landscape.

Python and other non-browser languages are far more powerful and expressive, and — since you refer to Python 3 — willing to further improve.

[ Parent | on HN ]