31–37 of 37 posts
Earlier quoted context omitted.
I'm not sure what country you are talking about. Inflammable means the same in every english-speaking country.
The commenter was making a comical reference to Yakov Smirnoff: https://en.wikipedia.org/wiki/What_a_Country !
Earlier quoted context omitted.
Did you read the GitHub thread on Express? The project is still very much alive, but its internals have been broken out into standalone packages, so the only commits to Express itself are version updates. That issue was created based on a misunderstanding.
If you read further down on the Github thread, the guy who did the splitting out is no longer working on the project and it's now fully in IBM's hands, who aren't doing much of anything.
Between this and the other article regarding the death of ExpressJS-- is IBM is a good contributor to the JS open source community?
Did you read the GitHub thread on Express? The project is still very much alive, but its internals have been broken out into standalone packages, so the only commits to Express itself are version updates. That issue was created based on a misunderstanding.
One might reasonably wonder whether executing npm outside a sandbox is a good idea under any circumstances.
But they can't be stealing any identifying information right? At best it can count the number of times the package was downloaded. Isn't the solution for npm to have tighter controls on where it will download packages from?
This is why you should always shrinkwrap and run a private npm repository in production. Anything less is opening you up to remote takeover at the whim of a single package publisher.
Should the HN title include "(2015)"? This StrongLoop issue was reported in February 2015.
In the meantime, if you use a Strongloop package, fork it and remove the optionalDependency.
Between this and the other article regarding the death of ExpressJS-- is IBM is a good contributor to the JS open source community?
In their usual fashion they link to internal bug trackers when committing (without summary), something that has frustrated me greatly while attempting to work with them on strong-remoting and loopback-explorer.
I have long since come to the conclusion that most of the nodejs ecosystem is rotten. I don't even know where to begin. I'm certain this is a mentality issue more than anything.
I just think that the nodejs ecosystem moves fast. But anything involving StrongLoop/IBM is immediately suspect.