node.js is the new java

it greatly improves on it's predecessors
familiar syntax
it's designed to be practical, to the chagrin of CS purists
next-generation of applications being built (hadoop, palantir, runsecape :  asana, meteor)

>>36
Ergo your wrong bitch.
No, it's my right bitch.

>>41
Welcome to /nipples/ enjoy your stay

>>4
point.prototype.add
Babby's first non-class-based language

Duck my chebs

>>43
babby's first can't-do-operator-overloading language

>>45
What did you expect from a LISP?

>>46
LISP doesn't have operators, aside from the more meta evaluation things like ,`'@().

>>47
That's the point.

>>48

I see.


Fun fact. Did you know symbols in lisp can have white space in them?


(define I\ bet\ you\ can\'t\ do\ this\ in\ that\ other\ language\. 34)

>>49
window['I bet you can't do this in that other language.'] = 42

>>50
I think you meant:
window['I bet you can't do this in that other language.'] = 34

>>51
I think you meant:
window['I bet you can\'t do this in that other language.'] = 34

>>43
Symta isnt about OOP at all. Symta is about:

// takeInit odd? [1 5 1 2 3 1 1 2 3] --> (1 5 1)
takeInit P [@Xs @nb,P] = Xs

>>50
I am impressed.

You can do that in lua too.


_G['I bet you can't do this in that other language.'] = 31

>>54
thing is, nobody would use that piece of shit when they could use javascript instead

>>55

there are things that lua can do that javascript cannot, and places lua can fit in better than javascript would. It would be silly to use javascript for some of the applications that use lua for the same reason it would be silly to use lua for client side web scripting.

>>56
like what

show me what you got, brfag

Javascript is good because it can run anywhere. We have no other choice for client-side web programming. So we learn to deal with its inconsistencies. Some learn to love it. But it's ultimately a bad language. You can't think about the future of the web and come to the conclusion that Javascript will still be there. Javascript is not suited for the web as an application platform. HTML5 tried to fix this--but it still relied on Javashit. Microshaft had the right idea with ActiveX. It was just too non-portable and difficult to use to have widespread adoption (although a lot of good browser-based software uses ActiveX because it just works).

The real problem with node.js is the assumption that we likes writing in Javascript. We use Javascript only out of necessity.

*like

a lot of good browser-based software uses ActiveX
Really? Name one. Keep in mind that it has to be ``good".

>>57

It's a barebones scripting language that can be embedded into other applications. It's fast, simple, easy to write and learn.

https://en.wikipedia.org/wiki/Lua_(programming_language)#Applications
https://en.wikipedia.org/wiki/Category:Lua-scripted_video_games

It has also picked up its own inertia in acceptance. Like how you will learn javascript if you are getting into web development, you will learn Lua if you are getting into video games or want to customize an application that offers lua scripting. In a way it is a standard customization language.

>>58
Now you understand the true meaning of the word "forced". And if you refuse, then some other shabbos-goyim will do the job - Earth is full of conformists, who will happily suck any Jewish dick and say "thank you, Shlomo".

>>62
die in a fire, cretin.

>>60
Inferno, and thats it... the rest aren't likely good at all, after all they're still using ActiveX in 2012.
Considering that it has been severely limited to a legacy API solely to allow plug-in type things like Flash to work from IE7 onward, this might explain why IE6 is still around on corporate machines... to run some in-house shit written in VB.

async is fine. callback hell is entirely inherent to your ability as programmer, not to the merits of the platform. learn how to compose functions already faggots

>>63
Shalom!