It's even worse than it appears.
I don't know if anyone else finds NPM to be unreliable, as I do, over many years. Here's a scenario. I have to make a minor change to a package. So I increment the version in package.json, and npm publish it. Then in the app that's using it, I do an npm update. The update happens. But the app doesn't get the latest version. Something is cached somewhere, because if I look in the node_modules folder, the new version is there. I've resorted to using a lib folder and keeping a copy of the package updated there. But of course I'm reinventing npm in scripts by doing this. Sometimes NPM works as I understand it should, but every so often it goes crazy like this.#
The NYT needs a real public editor, a member of the public who is not a journalist, and has unfettered access to the op-ed page, and can provide perspective for other readers and for the writers and editors.#
I groan when passwords are required to have at least one uppercase letter, one lowercase, a number and/or a special character. I know as a matter of math that these requirements doesn't make passwords better. Does it help people who type asdf as their password come up with more random strings? Also I hate sites that make me create a new password every so often. I can manage that myself. I suppose maybe they're saying hey we were hacked recently and are requiring everyone to change their passwords instead of making a public statement.#

© 1994-2019 Dave Winer.

Last update: Saturday August 17, 2019; 7:00 PM EDT.