I would dispute that I am trolling or starting arguments here. There's that time I was rude because that article hit a spot I've contended with repeatedly when training juniors (and possibly some alcohol was involved) - but apart from that, I would appreciate any pointers as to why you'd conclude I'm in bad faith. This is very unconducive to interesting conversation and I would like to work on that.
You're making a distinction I'm not, whether they signed off on it directly or indirectly, thanks for pointing that out. I don't really see the difference as that important though, in the end it's their procedures that are meant to safeguard against this, and they failed. Believe it or not, I have no motivation to incite an argument or anything of the such, why not simply assume I'm mis-informed but in good faith, and correct me ? Anyway thank you for the details about the DOT etc, that's what I was asking for.
My point is that it was their job to catch this before the plane was commercially used. While I expect no one to be perfect, I do expect some introspection as to why this went through the cracks. Why is this unreasonable ?
I do regret somewhat the name calling. But if I were to publish an article with such incredible arrogance and pretension as to judge two of the major techs of the decade, and did so without applying either correctly, I would welcome some name calling. I think the intolerance to this is something of the neurotypical.
I don't really see those as issues... The hub chip is cheap and doesn't directly do i2c, but, so ? Controlling VBus seems to be by design, exactly for devices that are separately powered to still work: see author's other project https://github.com/JimHeaney/usb-toggle . There should be a way to block further communication at the software level if that matters to one's use case. You can expand this, just plug a bunch of them into another hub...
Definitely have an in depth read of iTerm2's documentation (<https://iterm2.com/documentation.html>), at the very least one of the feature page (<https://iterm2.com/features.html>) - I know it sounds weird, but it's so far ahead of other terminals that it's hard to imagine, and expectations are blown. The trigger feature for example is fantastic too.
iTerm2 has great build in support for it. You just cmd-click and hold a file and it's as if it was sourced from any other ui app. You can even get it to work with remote files both ways, including dropping a file on an iTerm2 window during an ssh session and it can scp it over for you. (yes needs some shell collaboration, but it's trivial to setup)
I'm not saying you should at any other diff than that of the lockfile itself. From there figure out potential impact, run more complete tests, and other mitigations are available. In most famous instances (leftpad and this newsline), the problem would have been immediately obvious. Just because it's still possible to fall victim to sabotage doesn't mean you shouldn't be doing this.
Well I think it was introduced in npm 6, either way you slice it, 6 major versions is way to late for this basic functionality.
Yes but that is the issue with yarn: it has its separate lock file, which is why when I (used to) devops node apps, I required the devs all agree on either npm or yarn but not a mix.
npm ci is relatively new, before that it was hard to get it to precisely respect the lock file. There is also an issue if your devs don't all decide to use either yarn or npm with the separate lockfiles.
The way you do it is simple. Take ruby gems. In development you update as often as possible. When you see the lock file changed, you check you're happy with the upgrades and commit the lock file. When you don't want to keep the newer version, you change the gemfile (package.json) to point to a version you're happy with, ideally with a comment describing why you're pinning, and what you'd have to do to adopt the newer version. In CI/CD you exclusively use the lock file. This workflow is very difficult to emulate with npm/yarn.
Alright, eugenics wasn't the right word. But still this isn't evolution in the same way getting a medical intervention isn't. If you want to include everything we do as part of evolution, which is a defensible position, then all murders would be natural, this is not a practical perspective for a society.
Complete layman here, every 6 months or so for the past decade I see an article claiming someone got air-less tires working. What are the chances this would be it ?
But if the licence is that cheap, they're showing their hand, the difference between a protection scheme and IP protection here is incredibly murky. Even if you didn't aim to help others not be bullied around, going for a settlement seems the smarter option.