morphine wrote:Actually, from someone who earns his food doing this sort of thing... I haven't yet begun to you use it, but everything I've seen about node.js makes it look all kinds of cool and I'll dare saying that it has a nice future.
I don't dispute that, it does cool things and everyone seems to want to use it. But there are lot of competing things that are equally cool and have not only bright futures but bright pasts...
morphine wrote:You see, the thing is that basic Javascript is pretty terrible, but not because of a problem with the language. It's mainly a problem with the ever-shifting, unpredictable and inconsistent functionality that the browsers expose to JS. However, node.js sidesteps this - browser issues and API inconsistencies won't (I hope) be a problem on the server-side.
Only because google did a ridiculous amount of heavy-lifting to create V8, which node.js uses. It seems to me that something must be wrong with it if it is only usable when other people have had to put massive amounts of effort making it acceptable. It's the same even with the libraries, lots of people use javascript, sure, but only really via jQuery.
My point is that, if you have to abstract/work-around virtually about the language,
why choose that language? There are plenty of similar frameworks and stacks that are built around other languages, but yet you can still easily use the native language they were built on. No one seems to actually want to use javascript like that, so why, oh why, choose javascript?