893 karma · joined September 12, 2022
They did check and it was in the trainingset but they could not confirm if it was the /cause/ of it, which is a bit of a cop out.
I'm not sure what exactly this refers to (because of the paywall), but revoking right of travel before trial is fairly common, it the US it would be classified as detained without bail. And happens when there is a reasonable concern for flight risk before trial as seen by the judge.
Only ST, NXP, Nexperia, Osram, and a bunch more obscure ones. It's not a boom, but it's far from a wasteland
No, contributions are handled by the employer/company
It highly depends on your own perspective and goals, but one of the arguments I agree with is that habitually using it will effectively prevent you building any skill or insight into the code you've produced. That in turn leads to unintended consequences as implementation details become opaque and layers of abstraction build up. It's like hyper-accelerating tech-debt for an immediate result, if it's a simple project with no security requirements there would be little reason to not use the tool.
[0]: https://www.forbes.com/sites/traversmark/2024/05/17/why-kids...
For my perspective, my experience with btrfs has been flawless through 11 machines and at least 3 major releases on each without any maintenance but it could just be I'm not hitting the worst case (only use snapshots on 2 machines, raid on 3). And I've only used btrfs since fairly recently (~4 years now). I've had to recover one drive of a friend using the method I outlined before as he filled the entire drive with media. For me the trade-off of a few rough edges but more functionality & flexibility than other filesystems is worth it.
For your update issue, I think you're mostly correct; the package manager likely assumes the filesystem is not snapshotted (i.e. it will reclaim disk space), while btrfs with snapshots/CoW will use the entire size of written files unless it's in the same snapshot.