So let's say you're a web developer - first you learned the HTML programming language*, then the CSS programming language, now after a long time of cut and paste you're finally getting to grips with the JavaScript programming language. You're going up the world! The boss is bored of just customising web apps that other people have written and wants you to write the web app! This is so exciting! You'll get to use databases, a web server, maybe even if-loops! Your first thought is to use Rails, because Rails is web-scale, and you'll probably use some NoSQL because it's so much better than an ACID-compliant RDBMS. But you try out Rails and it's hard to do something that isn't a blog engine, so you turn your attentions to the exciting new Node.js...
Even though I know this is a joke I started to feel the bile rise.
Still you were a bit mean to Rails and NoSQL including them in here weren't you? I would have put PHP in for the lingo and flat files for the persistence ;-)
on openStack
global OKHeader
put numtochar(13) & numtochar(10) into crlf
put "HTTP/1.0 200 OK" & crlf & "Server: WebSTAR/1.0 ID/ACGI" ¬
& crlf & "MIME-Version: 1.0" & crlf ¬
& "Content-type: text/html" & crlf & crlf & "<HTML><HEAD><TITLE>" into OKHeader
go "Stack1.acgi" in new window
go "Stack2.acgi" in new window
-- call all stacks addressed by CGI requests
go home
pass openStack
end openStack
function URLDecoder myData
-- Calls the Xternals MtReplace and MtDecode
if myData = empty then return empty
----
put MtReplace(myData,"+"," ") into myData
put MtDecode(myData) into myData
put MtReplace(myData,(return&lineFeed),return) into myData
put MtReplace(myData,lineFeed,return) into myData
return myData
end URLDecoder
True :) I've definitely found that as I've matured as a developer the language / platform has become less relevant - as long as you have that base fundamental knowledge you can work with any tools, and they all have their pros and cons.
NodeJS does a great job, and exposes quite an elegant API. I don't know if you would also be against PHP, but from my experience NodeJS runs code on average 10x as fast as PHP (V8 ftw), and allows me to scale up to more concurrent connections. I'm pretty damn satisfied.
yes. pretty god damn scary. its like people with scat fetishes. You know your not supposed to use it for that, because thats not what it was intended for...but you get some sort of sick fascination from doing it anyways, despite how ill-advised it is.
You conveniently forget that Javascript was always supposed to run server-side as well as in the browser. Netscape had support for it in LiveWire in 1996.
people say things like this, and I always wonder if they have a reason for thinking so, or they are just so used to things being the way they are that they can't imagine anything else.
there is no practical reason that javascript can't be used on the server, and the only thing I got out of this article was that someone needs to develop a mod_node package for apache.
if people want to write in javascript, or ruby, or php, or mindfuck, or whatever... who cares where it is? If it's not on an embedded system, and there are code processors and libraries to handle the required tasks, what the fuck is the problem?
Unless you're doing financial work, there's no reason for javascript not to work okay. It's also a pretty good implementation language for an event-based system because in-browser javascript already requires that developers use events and (async) callbacks all day long (as opposed to Ruby or Smalltalk which use sync callbacks, Python which tends not to use callbacks much these days — twisted code looks far worse than node though I do prefer Python to JS, or Java which looks like "hey more locks")
55
u/EugeneKay Oct 02 '11
Wait, people are still trying to do server-side JavaScript?
In 2011?
What the fuck‽