The fact that yarn had to come into existence really only proves my points, I feel. Sorta funny that their web page doesn't simply sum it up as, "yarn is [hopefully?!] a real, actual, package manager, instead of that horrible, just horrible, pack of lies called npm."

I say [hopefully?!] because the Migrating from npm page made it look to me like I could just do something falling off a log easy (and that is what any tool that is trying to help people get away from npm should aim for):

$ sudo npm install -g yarn
$ yarn install

but of course that didn't really work for me:

$ yarn install
yarn install v0.21.3
info No lockfile found.
error Error parsing JSON at "/home/x/package.json", "/home/x/package.json: Unexpected token ,\".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
and

$ yarn

gives me the same error. So that's nice. Because you wouldn't want to, you know, tell me the line number that the problem is on. Or, you know, be able to handle the (crappy, natch) comment style from npm's package.json. Or just, you know, kinda not completely suck right out of the box. (Don't even get me started on how everything defaults to being colorized with escape codes all over the place these days, since I am an emacs user.)

I guess the whole "gosh I want to be able to comment things in any kind of sane way" idea is just too old school for anybody to make it all suck less? Because it sure seems to still suck afaict.