31–40 of 108 posts
I wish companies would do away with the "leaving to pursue other opportunities" nonsense and just give no reasons if they don't want to discuss it. No C-level exec resigns "effective immediately" without either a transition plan in place or something concrete lined up. I get wanting to allow him to say he resigned instead of he was fired, but the silly language of the press release just makes it worse.
I’m fascinated by the fact that while node has become a new standard in the industry , and the project is receiving lots of supports from all sorts of companies ( IBM , Microsoft etc...) absolutely no discussion has been opened about how much at risk the JavaScript ecosystem actually is with « npm » and it’s weekly dramas Not a month pass without something going wrong inside of inc, millions of developers are dependa…
The people that would care the most are mostly immune to npm issues. Privately hosted npm repos, checked-in to version control systems, etc. There are plenty of solutions if you don't like npm. However, they carry the traditional costs of managing dependencies; if you want super super super easy above all else, that's what npm does.
I’m fascinated by the fact that while node has become a new standard in the industry , and the project is receiving lots of supports from all sorts of companies ( IBM , Microsoft etc...) absolutely no discussion has been opened about how much at risk the JavaScript ecosystem actually is with « npm » and it’s weekly dramas Not a month pass without something going wrong inside of inc, millions of developers are dependa…
Earlier quoted context omitted.
> I wish companies Because it's not a soap opera and you're not owed anything about the personal business of other people. As an individual, I have every right to control the narrative for why I've left a company (assuming nothing illegal).
That's my whole point. I fully understand not wanting to air everyone's laundry. I'm just suggesting that nobody is buying their silly lies, so if they think they are "controlling the narrative" they are sorely mistaken.
Under Bryan Bogensberger's leadership, npm lost: - its CTO - its COO co-founder - some fantastic people in the JavaScript community - a federal labor dispute - its culture - its reputation - its business model to Github
From the Register...
"According to people familiar with the matter, Bogensberger was asked to leave by the company's board of directors." [0]
For more context...from Jonathan Cowperthwait, NPM's former vice president of marketing...
"Many of us spent the last year watching our friends and colleagues' struggle through our fingers, but I'm still profoundly confident in the company's ability to turn this around. Sometimes bad executives happen to a good company." [1]
[0] https://www.theregister.co.uk/2019/09/20/npm_ceo_bryan_bogen...
[1] https://www.businessinsider.com/npm-ceo-bryan-bogensberger-r...
Under Bryan Bogensberger's leadership, npm lost: - its CTO - its COO co-founder - some fantastic people in the JavaScript community - a federal labor dispute - its culture - its reputation - its business model to Github
They had a business model?
Under Bryan Bogensberger's leadership, npm lost: - its CTO - its COO co-founder - some fantastic people in the JavaScript community - a federal labor dispute - its culture - its reputation - its business model to Github
They had a business model?
I’m fascinated by the fact that while node has become a new standard in the industry , and the project is receiving lots of supports from all sorts of companies ( IBM , Microsoft etc...) absolutely no discussion has been opened about how much at risk the JavaScript ecosystem actually is with « npm » and it’s weekly dramas Not a month pass without something going wrong inside of inc, millions of developers are dependa…
Yes. The Node ecosystem is a huge liability just waiting to happen. Any organization that depends on NPM is making a huge gamble. You can do a lot to mitigate this (private NPM repo, locks) but the reality is that the dependency chains are dangerous. Is someone in an organization going to audit all of those dependencies? Especially under the circumstances where they've been declared without an explicit version (>, >=…