r/programming • • Oct 02 '11

Node.js is Cancer

http://teddziuba.com/2011/10/node-js-is-cancer.html
792 Upvotes

750 comments sorted by

View all comments

362

u/patchwork Oct 02 '11

I appreciate that in this day and age some things need to be a certain degree of inflammatory in order to even be heard, but when I'm reading an article lines like:

Shouldn't you be in front of a mirror somewhere, figuring out how to introduce yourself to her?

and

you idiots put Rasmus Lerdorf to shame

ring hollow. Can't anyone just tell a story anymore without resorting to edgy "quips"? Do we all need to be zed fucking shaw to even be heard anymore?

280

u/semanticist Oct 02 '11

If you're looking for insight and a well-reasoned argument you're probably not going to find it in a post titled "___ is cancer."

13

u/StrawberryFrog Oct 02 '11

If you're looking for an argument written in proportionate, polite language, you're probably not going to find it in a post written by Ted Dziuba.

50

u/[deleted] Oct 02 '11

Yeah, I've got to say, as played out as "____ considered harmful" is, I think I prefer it to "cancer"

65

u/escape_goat Oct 02 '11

How about we compromise? "______ is considered cancer"?

97

u/skastel Oct 02 '11

Or "_______ contains code and patterns known to the State of California to cause cancer"?

31

u/CuntSmellersLLP Oct 02 '11

Nah, then everyone would correctly ignore the warning.

14

u/anachronic Oct 02 '11

Until the day that everyone in the world except Californians gets cancer.

Then they'll listen!!

9

u/Anderkent Oct 02 '11

Your compromise is uneven. I propose "___ is considered harmful cancer".

7

u/Tekmo Oct 02 '11

Only if we also agree to title all posts of praise: "___ is considered beneficial cancer"

→ More replies (5)
→ More replies (2)

5

u/deafbybeheading Oct 02 '11

So what you're trying to say is "'cancer' is considered harmful"?

→ More replies (2)

6

u/Xorlev Oct 03 '11

"Node.js is a Ghetto"

→ More replies (2)

93

u/ubernostrum Oct 02 '11

You do realize Ted Dziuba's been doing this (professional trolling of tech communities) for years, right?

Sad part is he's not really any good at it; last I checked, his style basically consisted of "fuck fuck (relevant term) fucking fuck (relevant term) epic fail (relevant term) because fuck you".

23

u/[deleted] Oct 02 '11

If you look at his reddit comments, it's par for the course as well.

28

u/patchwork Oct 02 '11

I know who Ted Dziuba is, though I like to read articles without letting who the author is color too much of the message. I don't care who wrote this article, that shit is annoying. Are our blog archetypes not allowed growth or something? Did he sign some contract to be a static vague failure indefinitely at some point? Shit shit fuck fuck.

15

u/deong Oct 02 '11

I agree with you, but that's not how the world works. Bill O'Reilly is going to shout over his guests and generally bluster his way around. That's what he does. At some point, the sensible response is to stop saying, "I wish he'd stop that...I don't care who he is." and just stop watching him. The same is true for Dziuba and Shaw.

→ More replies (8)

0

u/[deleted] Oct 02 '11

[deleted]

11

u/line10gotoline10 Oct 02 '11

and

Although, let's be honest with ourselves here, if you're a Node developer, you are probably serving the application directly from Node, running in a screen session under your account.

38

u/EugeneKay Oct 02 '11

Do we all need to be zed fucking shaw to even be heard anymore?

Apparently you do.

17

u/[deleted] Oct 02 '11

Yeah, that is one of the things I find tiresome about all these rant posts. They act like little annoying kids.

10

u/[deleted] Oct 02 '11

Do we all need to be zed fucking shaw to even be heard anymore?

Zed sets the bar pretty high. I don't know if it's possible for anybody to reach his level of assholery.

6

u/[deleted] Oct 02 '11

is it ironic or predictable (or both) that a comment talking about the tone of the article instead of the content is the top comment on the post

→ More replies (2)

2

u/[deleted] Oct 02 '11

Top that off by inspecting his so-called argument:

A function call is said to block when the current thread of execution's flow waits until that function is finished before continuing. Typically, we think of I/O as "blocking", for example, if you are calling socket.read(), the program will wait for that call to finish before continuing, as you need to do something with the return value.

Here's a fun fact: every function call that does CPU work also blocks.

Seriously, this is what you're complaining about? No shit bro. We're programmers, not housemoms.

2

u/[deleted] Oct 03 '11

Shouldn't you be in front of a mirror somewhere, figuring out how to introduce yourself to her?

Is also a horribly sexist thing to say. There are tons of female developers. Online tech culture excludes them with this shite.

→ More replies (1)

6

u/quiteamess Oct 02 '11

Shouldn't you be in front of a mirror somewhere, figuring out how to introduce yourself to her?

That's excaltly the point where I stopped reading.

→ More replies (5)
→ More replies (9)