A whole quarter of a century, or perhaps half of the entire software industries lifetime, of exciting known security errors to look forward to!
BRB, off to hide all my bitcoin under my mattress...
That would be a bad idea, and it's not just brevity.
- If com.facebook.hr has previously been published, would it mean that facebook can never have a division named HR?
- Once a company goes belly up, the domain often ends up with squatters/spammers. Domains with published packages will sell for a lot more in the underground market - for pure exploitation of rights to publish a newer version.
- In the absence of validation, nothing stops anyone from publishing com.google.exploitlib. And domain validation is friction.
- Most publishers on npm may not have a domain.
And finally like someone mentioned below, npm already supports scoped packages. https://docs.npmjs.com/about-scopes
Why not install `com.facebook.react’? Reverse domain notation is remarkably elegant given our internet. You are not typing ‘npm i com.facebook.react’ so often that it’s a pain. You probably use ‘create-react-app’ which is even worse.
Instead, every language creates a new cash grab for common names. And made it worse. New namespaces, new squatting. I can publish ‘react-racket’ and do whatever I want behind the scenes with it.
Case in point: do you add coffeescript or coffee-script.
Why optimise for keystrokes in your term instead of stability for your client? Jesus fuck.