Nodejs is so shit

>>52642046
what is cache?

>>52642046
Have you actually written a real app in it?

javascript should have never been used for all the shit people use it for these days. it's the new java except slower and buggier

File: 1357223526511.png (141KB, 313x313px) Image search: [Google]

141KB, 313x313px

>>52642071
nah dawg, go try it out for yourself. this is verified.

>>52642517
>writing serious applications in a toy language

>>52642046

>node is shit
completely verified.

But I'll still write in node or do a basic node based shell script with it. Sometimes living dangerously is just fun yo.

>>52642046

Actually, the only thing this proves is that the progress bar is shitty.

>>52642046
>Meme.js is a joke
No shit.

install ied and be fucking done with it.

fuck npm

>>52647508
Improvised Explosive Device?

File: tbh.png (3KB, 100x59px) Image search: [Google]

3KB, 100x59px

>>52642830
this

I'm not on top of trends, but from what I understand, retard programmers are writing *everything* in Javascript these days because that's all they can understand. Is that the gist of it?

>>52642830
Yuppers

>>52648742
Not sure why there became such a huge push. I guess because all the web dev automation tools came out to make things easier but just clusterfuck everything.

> Change 1 line of sass code
> 10 minutes of debugging npm so I can run gulp

>>52642830
>it's the new java except slower and buggier
What a retarded comparison

>>52642046
>shit based on jewvascript
>shitty
nowai

>>52648903
>I guess because all the web dev automation tools came out to make things easier but just clusterfuck everything.
now you know why mozilla is throwing out all features made in cpp and replace them with crap made in javascript

How can you justify build times over a minute in the current year?
I bet the program isn't even that big or complex

>>52649424
check the github-conversion: the "ui" is on the same thread as the installing/building.

so the constant updating of the progress-bar is slowing down the actual work. derp.

File: 1430935109720.jpg (43KB, 497x349px) Image search: [Google]

43KB, 497x349px

This can't be fucking real.
All that time lost waiting for npm installing or updating.

>>52645423
You absolute madman.

>>52649384
And enterprises of great pith and moment
With this regard their current turn awry
And lose
the name of action

File: get_out.gif (778KB, 480x360px) Image search: [Google]

778KB, 480x360px

>>52649447
> the "ui" is on the same thread as the installing/building.
fucking hipster garbage.

>>52649384
On a semi-unrelated no(d/t)e, what do you think are SJWs?
Are they cancer, or are they maggots?
Do they attack living-if-weakened body and kill it, OR do they attach themselves to the body that's already dead, and start devouring whatever's left?

File: 5645334796196.jpg (24KB, 366x367px) Image search: [Google]

24KB, 366x367px

>>52649547
more like tapeworm, keeping you slim and healthy

>>52649620
Yeah, parasites were on the list of options, too. I think it's just a matter of time until Mozilla/Github fail, though, so I guess it's something more vicious.

>>52649830
>SJWs get in and kill Firefox and Shithub
>there are no women in STEM, why are computers so sexist?

File: Computers_a1d0d5_513041.jpg (26KB, 450x200px) Image search: [Google]

26KB, 450x200px

>>52649868
Rakim figured out dat sheeeit long time ago.

>>52642046

Wtf is everyone really complaining about?
Not understanding Javascript? Or an unoptimised change to a package manager UI?

If it's the first one, read some books and ask yourself why almost every language has a JSON parser. If it's the second one, then spend a little time with the like of Aptitude on Debian, or Pacman on Arch. Austere to the point that it won't even tell you what actually broke.