Hacker News Reader

Comment by jakear | Hacker News Reader

Would you want all packages you're responsible for being taken over by whomever happens to be NPM's preferred forker in the event of your getting into legal troubles? I'd be strongly against that.

This should be handled the way any other fork happens: people create forks, other people audit them for stability and choose which to update their dependencies to. This isn't up to NPM to decide.

View on HN

Now Microsoft's preferred forker. Yikes!

I'd rather hear Microsoft's suggestions on libraries to use than some random Joe Developer. They have/had unethical business practices, but their tech is really good and they have very smart people working for them.

A lot of people are making fun of Microsoft but most of them don't know or appreciate that you can run software compiled in the 90s on the most recent Windows 10 1909 without problems. Microsoft's backwards compatibility is off the charts.

Try that with macOS.

Well... Windows 10 have the record of the being the only windows that breaks backwards compatibility sometimes. I saw Visual Basic 5/6 applications stooping to work because Microsoft break something on a update.

Also, good luck trying to run any Windows 16 bit application on a modern Windows 64 bit installation.

> Also, good luck trying to run any Windows 16 bit application on a modern Windows 64 bit installation.

The officially supported method is to have Windows 10 (32 bit) running in HyperV. There is no 16 bit support in Windows 10 64bit builds.

I can run Ubuntu now without worrying about hardware compatibility and I can play video games, all from Windows. I'm a fan.

Something like that happened with `leftpad` in 2016.

Reply on news.ycombinator.com