Hacker News Reader

> it frequently breaks MAX_PATH on Windows and Linux

I've never heard of MAX_PATH issues in linux with NPM

> And the alternative is the newest NPM, which makes builds no longer deterministic.

Calling the latest version an alternative to the older versions is a strange way to word this. You mean the issues you highlighted are now non-issues. Also the non-deterministic quality has very good reasoning which they have written about in length. This is a bold criticism with no meat to back it up.

> That is the cherry on the fucking pie. Then why does Flux (which is going to be used with react at least half of the time) use pretty much the same message loop as Windows 1.0 ? Oops, that's right, because it's simple and efficient. That "hurr durr iz old iz bad" mentality is what is holding everyone in development back. Stop. That. Shit.

Have you ever used React? It's a strange criticism of react to go straight for flux, which is an optional design pattern which has sense fallen out of favor for redux based architectures

This is a low information rant that does little but show your lack of knowledge in these specifics. Though you have done an incredible job displaying how irrationally upset you are.

Sry for posting this here.. the post i wanted to answer was already flagged when i finished this lines...

Nice nearly a as high shit/fuck ratio as the author of the quoted article. I'm to lazy to quote all ur stuff so u'll hopefully get the context via empty lines.

We're using npm for a few projects here and actually never got these problems? Are u sure this is even possible on linux?

The comparison would also hold with for example java, but yes I picked the worst of them to make clear that "worst fucking language" was an overstatement.

It's the simplest instruction to install it on your local system. You won't deploy it that way - so your sys admin won't care at all.

A lot of people missconfigure their nginx/apache and struggle with stupid problems. Why should I need to setup a real server for development? Python for example has some lightweight alternatives to.

Actually I don't get that point. Dom is bad, react is one of many solutions and flux is great too. What is your argument again?

Actually this isn't true. It's more convenient to use javascript everywhere (web related) than "fucking around" with jquery or stuff like that inside html. Of course sometimes is makes more sense to have an python or whatever backend. We use python for our mqtt backed server side, but the frontend is pure javascript.

Actually this wasn't a rant. Your answer here was a rant.

>Nice nearly a as high shit/fuck ratio as the author of the quoted article. I'm to lazy to quote all ur stuff so u'll hopefully get the context via empty lines.

You apparently don't seem to enjoy my fucking style, So I'm going to go with shitty sarcasm instead.

>It's the simplest instruction to install it on your local system. You won't deploy it that way - so your sys admin won't care at all.

Executing untrusted code on your machine. From the internet. With no way of pinning the script.

It'd be nice if distributions had a way of installing software, preferably checked by multiple people, signed and not MITMable. We could call them 'packages', and use applications that could be named 'apt-get', 'aptitude', 'yum', and such. Maybe even with versioning. One can dream.

>Why should I need to setup a real server for development? Python for example has some lightweight alternatives to.

Why would I want to setup the same dev environment as my production environment? What could go wrong with two different environments, right?

>Actually I don't get that point. Dom is bad, react is one of many solutions and flux is great too. What is your argument again?

No argument there, just that yours was bad. React is good, so is Flux.

yes, i don't

yeah, we see how good this works in debian... always the newest things and versions out there

actually a year ago we used local vm's for this ... now we use docker to deploy, nothing on local and never had a problem with it. - but I see your point there.

Never said, flux isn't... still don't get it

>Have you ever used React? It's a strange criticism of react to go straight for flux, which is an optional design pattern which has sense fallen out of favor for redux based architectures

That is absolutely not a criticism of React. React itself is pretty good, especially compared to the alternative of plain ol' DOM. I'm perfectly fine with the Windows message loop. It's simple and efficient. That is however a criticism of an absolutely terrible argument from the author.

I'd like to nominate you as the Deadpool of HN, language abated, I do like the passion that your 'corrections' exude. And amen, just use whatever works. Programming is a means to an end.

I had a few questions lined up regarding your rant before I took a look at your "about" page. I now see that you're doing a fine job.

echo use whatever works for you

That sh execute a script you download over the internet without checking it first is something. It makes you laugh, it makes you cry, but -

>Stop. That. Shit.

You ok?

>> A package manager that pulls libraries with so many files that it frequently breaks MAX_PATH on Windows and Linux.

This was my first hint that Node wasn't all it was cracked up to be. I still use it, but man, when it breaks in Windows it is a (to coin a phrase my professor used to use) catastrophic failure.

FWIW: npm may be bundled with node, but node is not reliant on it. All npm does is put libraries in `node_modules` for node to require them. Node does not need npm to run, and node does not make npm a dependency.

This is akin to PHP deciding to bundle composer with it, just because it's the defacto package manager for PHP.

>> I don’t see why node should be worse than some of them… especially php? > Comparing a shit sandwich to a turd cake. They're both terrible.

Seriously, how can anyone take this argument seriously when you can't even criticize the article without throwing unwarranted jabs at clearly popular and heavily used languages and deduce them down to "turd cake" and "shit sandwich".

Get your head out of your ass.

Popularity does not make quality. PHP is used because it's available everywhere and attempts to keep running no matter what you throw at it, causing some fun headaches. Node is used because people are either fed up with PHP, or web developers who can't be arsed to learn a new language.*

Whether you agree or not with my hyperbolic comparison is not my problem.

*But also, the very small percentage of people who made a proper analysis and decided that PHP/Node/Ruby/Whatever was indeed, the right choice for them.

>Fan of semicolon free JavaScript

Ew. (yep, unwarranted jab. again.)

All languages have their strengths and weaknesses, it's your job as a developer to pick the one that best suits your tasks. To hate on a language without giving real uses cases is worthless and not worth anyones time to even bother taking you seriously.

You sound like a bitter kid who couldn't get something to work so you spend your time talking down about the languages because you don't understand them.

In the meantime, thousands of people have no problem working with their tools.

Man, this "bitter kid" and all the other comments you make are very sad. No ones more a ball of immature anger than yourself. PHP is indeed a "turd cake," it's always been. The facts are lost on business types like yourself, who think as long as it's built and it stands, you can go get 'em. Yeah true. But HN has actual passionate computer science people on it. So there's gonna be a reckoning. Can't really call an informed critic a bitter kid and get away with it.