This is not the experience that I have. I use vendoring heavily because it's nice to be able to review all the relevant code changes when Renovatebot updates a dependency [1], and to get a feel for how heavy or lightweight certain dependencies are. If vendoring was incomplete, I would see it trying to download missing dependencies at compile time, but the "go: downloading $MODULE $VERSION" lines only show up when I expect them too, e.g. during "go get -u" or "go mod tidy/vendor".
[1] Before you ask, I'm not reading the full diff on something like x/sys. Mostly on third-party dependencies where I find it harder to judge the reliability of the maintainers.
I'll throw in a +1, afaik vendoring is a complete and reliable solution here.
Go's `mod`-related commands have had quite a large number of breaking changes in behavior through the years, so I won't say it's a stable solution (aside from completely disabling modules, that has always worked fine from my use). I've had to fix build scripts at least once or twice a year due to that, e.g. when they started validating that the vendor folder was unmodified (a very reasonable thing to do, but still breaking). But once that is overcome it has always worked fine.
I remember a rule of thumb being "if you cannot remember the last day on which you did not have any alcohol, you're an alcoholic". Probably not what AA goes by, but I like the simplicity of it.
This is weird - my mother very rarely drinks but she’ll be hard pressed telling you exactly when was the last time time . This doesn’t make her an alcoholic.
Or should you start the rule with ‘you’ve been drinking everyday for a while’?
If can't remember the last time she DID NOT take alcohol, it does make her an alcoholic. Or just an old person with severe memory issues, who shouldn't even live alone at that point.
Can you stop tomorrow? If so, then no. If you make excuses why you can’t or shouldn’t, or when you try you have physical or psychological problems, then yes.
Oh hey, it's my favorite pet peeve. When flagging a potential conflict of interest, the word is "Disclosure". "Disclaimer" means "I'm just a random guy who cannot assume responsibility for what they're saying", like in IANAL.
It absolutely has to do with ACME. There used to be CAs that would generate a service certificate including private key for you. This is obviously a terrible idea, but it is made impossible by ACME only allowing exchanging CSRs for certs.
Only for devices that do not allow you to patch the CA bundle as an aftermarket repair. Call your representative and demand Right to Repair legislation.
That is ... basically all of them? Other than general purpose desktop/laptop computers that is. Show me a TV or smartphone that does allow you to push new roots to it...
Yes, that's exactly the problem. There's good reasons why any particular team doesn't onboard new engineers each day, going all the way back to Fred Brooks and "adding more people to a late project makes it later".
Wasn't most of that caused by that one change in 2022 to how R&D expenses are depreciated, thus making R&D expenses (like retaining dev staff) less financially attractive?
Yes, because US big tech have regional offices in loads of other countries too, fired loads of those developers at the same time and so the US job market collapse affected everyone.
And since then there's been a constant doom and gloom narrative even before AI started.
It's actually kind of the opposite with DB [1]: Regional trains are decently on-time, and commuter trains even more so because they usually have dedicated tracks. Long-distance trains and cargo trains are the ones with abysmal punctuality, the former because the schedules are so tight that a random passenger coughing at the wrong time can fuck everything up, and the latter because they have to yield when a late passenger train has to make up time.
reply