NPM Is Joining GitHub

Post by dlivingston » Mon, Mar 16, 2020, 11:50 PM UTC

Dahoon wrote: post #381

dlivingston wrote: post #217

Earlier quoted context omitted.

Care to explain? Safari has one of the highest standards compliance of any modern browser [0], which IE famously did not. It has been argued with various success [1] that Chrome is the new I.E., due to "Chrome exclusive" web standards. [0]: https://html5test.com/compare/browser/safari-11.2/chrome-30/... [1]: https://news.ycombinator.com/item?id=16070595

Want to try something fun? Install any browser in iOS and do a test. Then do the same test with Safari. Now ponder why they are exactly the same no matter which browser you install.

Post by aduitsis » Mon, Mar 16, 2020, 11:51 PM UTC

oorza wrote: post #356

Spivak wrote: post #239

Earlier quoted context omitted.

I think the honest truth is that a lot of developers see Safari similarly to IE because Firefox and Chrome are quick to jump on and ship new features and "if only Safari kept up" they could be used "everywhere". Combined with the fact that iOS is large enough that you can't just drop Safari support and tell them to use Chrome. It's a weird world where webdevs apparently ideally just want everyone on the 6 second old…

You're right, IE6 was amazing at the time. It made a ton of things possible that previously hadn't been, and the standards bodies were lagging behind it. Had MS actually kept updating IE6 and kept it ahead of the standards, the standards would never have mattered, and we'd never have developed this sick taste for IE. No one hated that they had a monopoly, we hated that they had a stagnant monopoly.

Post by jrochkind1 » Mon, Mar 16, 2020, 11:54 PM UTC

pkilgore wrote: post #308

skrebbel wrote: post #261

Earlier quoted context omitted.

> after we saw what happened to yarn I missed something, what happened to Yarn?

The maintainer released Yarn 2. Yarn 2 is pretty foundationaly different than Yarn 1, and can and does break a lot of products/projects if used. Some folks are not happy about it, although Yarn 1 will probably continue to be maintained by the community for a while. This seems to be pretty fair about the whole thing: https://shift.infinite.red/yarn-1-vs-yarn-2-vs-npm-a69ccf022...

Post by teknopaul » Mon, Mar 16, 2020, 11:59 PM UTC

quixoticaxolotl wrote: post #382

K0nserv wrote: post #185

Earlier quoted context omitted.

It depends on what the alternative is. When NPM starts running out of money to run the service what would happen? More VC, but only to a point and the firms would be increasingly be influencing NPM to make money by any means(probably not good for anyone but the firms). Alternatively a cash strapped NPM fails to invest in security and availability of the service leading to widespread outages or worse a large scale sup…

Change my mind: package management infrastructure run by government as a public service should be the ideal end outcome for everyone. Why I think this: private or volunteer models are unsustainable in the long run owing to funding uncertainties or conflicts of interest between stakeholders. Utilities that support the bulk of our technical infrastructure should be secured by public interests. Governments can keep thin…

Post by fastball » Tue, Mar 17, 2020, 12:03 AM UTC

ivanbakel wrote: post #361

greggman3 wrote: post #344

Earlier quoted context omitted.

Confused why you think a service servings millions or billions of requests a day wouldn't require money to run. Do you think some grant magically appear out of thin air to pay for the servers, storage, bandwidth, and maintenance?

Big leap from "servers cost money" to "a package manager requires a commercial entity". How are other language ecosystems and package managers operating, many without private companies attached, when they too are serving millions of requests a day?