Sure, I read that in TFA too. My point is that if USB transfers of Kindle eBooks are being sunsetted, I would estimate that Send to Kindle's days are also numbered.
I'm surprised that this is being dropped, but the "Send to Kindle"[0] feature is still supported. I would imagine that the email servers (and whatever other behind-the-scenes cruft it requires) to relay files to individual Kindle devices is a much bigger maintenance burden and "piracy" enabler than transferring via USB.
I'm a huge user of the Send to Kindle feature via my Calibre library too, so this has me pretty bummed and pessimistic for the future. I guess if the worst comes to pass, I can just look into jailbreaking or getting any of the zillion other Android-based eReaders from AliExpress.
Do you mind specifying the title of the paper? It appears there's quite a few papers[1][2][3] published concerning Therac-25 by an author named Leveson.
Very exciting! I'm particularly pleased to see the invisible encryption stuff mentioned.
One of the biggest pain points I had when setting up a self-hosted Matrix instance and getting all my devices signed in was the crypto stuff. At least in the client I use, Element, I was bombarded with tons of popups with vague "Upgrade your encryption!" prompts upon logging in the first time. The copywriting on the "Security & Privacy" page was less than helpful in illuminating what I was actually "upgrading" or setting up, since specific technical terms (e.g. recovery key/security phrase/security key) were all used more or less interchangeably. If that kind of confusion can be reduced or swept under the rug for end-users, it'd be a huge improvement on user experience.
Interesting post. I've used Laravel for a few years now for work and personal projects, and I've really enjoyed it. I tried to test out Rails to explore other MVC web frameworks, and I just couldn't vibe with it. I think the major areas in which I was incompatible with Rails were:
- Lack of dependency injection/inversion of control. I find it interesting the author lists this as an advantage. With Rails, I was always a little anxious not knowing where things were defined or being implemented.
- Validation happens on models, not requests. With Laravel, I really appreciate being able to validate pretty much any data coming into the application regardless of whether or not it ends up in the database. With Rails, I tried to look for something similar to FormRequest and its validation rules, but I couldn't find many solutions. I think it might just be one of those things that's not the "Rails way".
- Perhaps more of a Ruby issue than a Rails issue, but the dynamism of the language - especially in its type system - was a bit of a drawback for me. I really appreciate PHP 8 and newer versions of Laravel for their support in type hinting and static analysis; being able to mouseover anything and know pretty confidently what I'm working with is a huge boon in my productivity.
I definitely agree with the author on a lot of the Laravel tooling stuff. I've learned to just kind of ignore most of the offerings outside of the core framework. I'm sure it's all great, but there's always a bit of churn in Laravel as the author mentioned so I'd rather save myself the future heartbreak.
Ah, I think you're referencing the sidenotes. Sometimes the website doesn't render properly on mobile (I've tried getting click-to-expand working, but it's tricky), so try reading in desktop mode.
Regarding sidenote #1, I actually very deliberately did not mention the language or company ;) Here's the full text of the sidenote, if you're still unable to get it rendering:
> I'm not going to name the language itself, because this post would just turn into a flame war over that language specifically, and I definitely don't want to cast shade on any language/community in particular. I'm also kind of hoping that the most annoying people read this and think, "Ah, of course he's talking about that language over there! This criticism obviously doesn't apply to my perfect and favorite language!" Regardless, I feel that the thesis and content of this post applies pretty evenly to most functional programming languages.
> As I said, the problem is a classic one; it was formulated during the war, and efforts to solve it so sapped the energies and minds of Allied analysts that the suggestion was made that the problem be dropped over Germany, as the ultimate instrument of intellectual sabotage.
Oh yeah, I had just heard about Talos Linux the other day in this blog post[0], and it seems super interesting. If I was all-in on Kubernetes, I'd probably consider it strongly. Unfortunately, though, there's other stuff that I want to run on the machines outside of the k8s cluster (like the BIND server I mentioned in the post).
Same, I originally had a bunch of RasPi's in my lab running differing versions of Raspbian until I got tired of the configuration drift and finally Nixified all of them. Writing a single Nix Flake and being able to build declarative SD card installation images for all of them makes managing a bunch of different machines an absolute dream (tutorial here[0], for those interested).
The only issue is remotely deploying Nix configs. The only first-party tool, nixops, is all but abandoned and unsupported. The community driven tools like morph and deploy-rs seem promising, but they vary in terms of Flakes support and how much activity/longevity they seem to have.
I agree. For most people just starting out, it's a lot more worthwhile to get a single cheapo repurposed desktop or a single Raspberry Pi to run PiHole or something on and then expand from there. My homelab[0] started as a single Pi running PiHole and has expanded to four machines running everything I need from Jellyfin to Calibre to DNS, etc.
That being said, when I finally got around to rackmounting and upgrading some of the other hardware in my lab, this "beginner"'s guide was really helpful.
It's seriously astonishing how much progress has been made in the past few years regarding gaming on Linux. When I first made the jump to using Linux as a daily driver circa 2016, I had to keep a Windows partition to be able to play any game in the Steam library that wasn't native on Linux. With steady improvements to Wine and Valve's release of Proton however, I can play most games out of the box or with a minimal amount of tweaking.
However, the games industry is still largely hostile to gaming on Linux. I've always had the best experiences with indie games or FOSS projects, and the only trouble I've had is with newly released AAA titles. I wouldn't even bother with newer multiplayer-only games or MMOs, as anti-cheat on Linux is a pretty reliable way to be falsely detected and instantly banned (not to mention requiring kernel-level access, which is utterly ridiculous).