In fairness, “I don’t want to maintain bindings for a language I never intend to use” is a perfectly reasonable position.
The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).
The problem with this take is the assertion that LLMs are going to take the place of secretaries in your analogy. The reality is that replacing junior devs with LLMs is like replacing secretaries with a network of typewriter monkeys who throw sheets of paper at a drunk MBA who decides what gets faxed.
There’s Finamp, a music client for Jellyfin with offline playback. I’ve not used it personally yet, but with Spotify ratcheting up prices again I’m in the process of switching to self-hosting my music library. When that’s up and running it’s at the top of my list for Android clients.
Perl is definitely a WORN language.
Write Once, Read Never
Rollout policies are the answer, and CrowdStrike should be made an example of if they were truly overriding policies set by the customer.
It seems more likely to me that nobody was expecting “fingerprint update” to have the potential to completely brick a device, and so none of the affected IT departments were setting staged rollout policies in the first place. Or if they were, they weren’t adequately testing.
Then - after the fact - it’s easy to claim that rollout policies were ignored when there’s no way to prove it.
If there’s some evidence that CS was indeed bypassing policies to force their updates I’ll eat the egg on my face.
API access was only half the problem. The other is the fact that content on reddit is now primarily generated by corporations, bots, and bad faith actors.
Going there for specific threads (e.g. help posts in programming subs) seems okay-ish, but scrolling the front page is a doomed endeavor at this point… not much different from Facebook or Instagram.
Subscribe
And his sister, the famous arsonist Anita Mcburney.
Ok that’s just not true at all.
Core temps ramp up astonishingly fast on RPi!
ducks
If their official website isn’t https://batsh.it I’m going to be very sad.
Edit: ☹️
Guys I found the GNOME dev!
“Hermit in a log cabin” is my retirement plan. If I could WFH from a log cabin I definitely would.
You should know that not all clients display your display name, some only show your username@instance.
It’s not apparent to everyone that your name is Onno.
There is no original thought.
A friend of mine had some explaining to do when he screwed up a dhcp config change and started routing his guest wifi through his “personal” pihole instead of the restricted guest one (he had family/children over often and did not want to be the reason nephew Timmy got an eyeful of wet bush or a beheading).
His family-friendly pihole was at holypi.lastname.local and his private one was creampi.lastname.local
See, even ping hates “consistent device naming!”
The other poster said it’s about convenience but that’s not really true. The claim to fame for NVMe drives is speed: While SATA SSDs can theoretically run at up to 500 MB/s, the latest NVMe drives can hit 7000+ MB/s.
It’s for this reason that you should pay attention to which NVMe drive you choose (if speed is what you’re after). SATA-based M.2 drives exist – and they run at SATA speeds – so if you see a cheap M.2 drive for sale it’s probably SATA and intended for bulk storage on laptops and SFF PCs without room for 2.5" drives. Double check the specs to be sure what you’re getting.
If you’re practicing 3-2-1 backups then you probably don’t need to bother with RAID.
I can hear the mechanical keyboards clacking; Hear me out: If you’re not committed to a regular backup strategy, RAID can be a good way to protect yourself against a sudden hard drive failure, at which point you can do an “oh shit” backup and reconsider your life choices. RAID does nothing else beyond that. If your data gets corrupted, the wrong bits will happily be synced to the mirror drives. If you get ransomwared, congratulations you now have two copies of your inaccessible encrypted data.
Skip the RAID and set up backups. It can be as simple as an external drive that you plug in once a week and run rsync, or you can pay for a service like backblaze that has a client to handle things, or you can set up a NAS that receives a nightly backup from your PC and then pushes a copy up to something like B2 or S3 glacier.
deleted by creator
Ted Ts’o was way out of line in that conference and was clearly channeling his inner ca. 2001 Torvalds.
I think Rust is a better path forward for a majority of the kernel/driver code maintained currently, but it is definitely going to take time for it to gain a foothold. I also think there is some condescension on both sides that is completely unjustified and needs to stop.
The hardline C devs that don’t want to learn Rust need to accept that at some point they will have to either adapt or pass the torch, and that no amount of whining or bitching in public forums is going to change that.
The Rust devs that are getting upset because people are “attacking” their favorite language need to accept that there will be substantial and impassioned resistance to making broad language changes to a set of projects that have existed for decades. It would be an uphill battle for any language to try to supersede C in the kernel; this is not a condemnation or attack on Rust or its zealots, it’s a matter of momentum and greybeard stubbornness.