> Why do you treat adding a feature (npm compatibility) like you’re losing something? Because you are losing something: a better ecosystem. Standardizing aroun

> Why do you treat adding a feature (npm compatibility) like you’re losing something? Because you are losing something: a better ecosystem. Standardizing around… standards is a good thing. When I dive into the dependencies of any given Node app it’s a mess of transpiled code, sometimes minified even, there’s no guarantee what API it’ll be using and whether it’ll run outside Node (is it using the W3C streams API or the Node streams API?). But inertia is a powerful force. People will just use what’s there if they can. So the ecosystem never gets made. > But it turns out that few people care that much about purity, so it’s fortunate that they’re not relying on that. By that logic we never build anything newer or better. Python 3 is better than Python 2 and sets the language up for a better future. Transitioning between the two was absolutely torturous and if they just prioritised popularity it would never have happened.