Important safety features ("do not generate child porn", "statements should be factual or backed by evidence") were simply not part of the design of these systems and have yet to truly solved to this day, but AI companies decided to release these technologies onto the general public regardless of their glaring flaws.

I like AI for its shitposting capabilities and its neat parlour tricks, but I also believe so far it has been a net negative for everyone but the richest minority of society who benefits from firing people and having computers do half their jobs badly. It's too late now, but in hindsight I do agree that these systems were too dangerous to release in this shape.

After correcting, for me, it flagged "jd-gui", but I had actually installed "jd-gui-bin" about two hours before the compromise. As far as I can tell, I was lucky that I felt lazy that night and went for the -bin package instead of waiting for the source to be compiled.

Given the way AMD has been treating this issue, I'm assuming they're just incompetent, though.

Accessibility technology like reader mode is once again proving its worth.

Add some outrage over bike paths (for or against) and this post will circulate reddit for weeks!

From what I can tell, the affordable BD players cannot play all discs. They can read (and probably write) all data discs, but when I buy a disc, there's no guarantee I will be able to rip it and make it accessible over my LAN. That's the kind of drive I want, and that's what ends up getting scalped.

Things like "this is a holiday in country X but only for people living in province Y except for in town Z" are massive pain to script. Plus, if the issue tracker and source control automation were working correctly, I wouldn't need to read the status of both to get a good understanding of the situation. Any time scripting there should probably be spent (by someone else) on fixing the problem in the first place.

When Claude eventually doubles or triples the token cost to stop hemorrhaging money, I'm going to lose these scripts and I won't be upset about it in the least. But until then, my "somewhat understanding of context" script-but-not-really setup is proving quite useful.

I can take a $120 gamble to just buy a USB BD-drive and hope the disc isn't DRM'ed enough to make it a problem, but I'd rather just be sure and grab a drive that can rip everything. Unfortunately, because we can't have anything nice, scalpers make these drives impossible to obtain.

Nothing I can't do myself (and generally I do keep an eye on that sort of thing), but it did catch a holiday for my foreign team members that seemed to have gone unnoticed, and remarked about a status mismatch between Jira and source control that made the dashboard misrepresent progress. It's not much, but it's an extra little check that works quite well.

Another trick I'm experimenting with is having Claude rebase my open PRs waiting for review every day, and auto-solving conflicts when they arise. I don't trust it enough to let it push code to the repository, but I think I have the prompt set up in such a way that I might soon start using it.

For normal people, there are three computer operating systems: Windows, Apple, and ChromeOS. Nvidia isn't going with ChromeOS and Apple hates their guts, so Windows is the only normal operating system they can market.

Their marketing makes clear that these devices aren't the piddly Chromebooks that ruined the desktop experience for so many people (expensive Chromebooks were nice, but rare in practice).

Qualcomm promised Linux support, failed to deliver, and now anybody burnt by their promise won't want to buy their hardware again. If they promise a Windows PC, people won't have reason to complain when Linux or FreeBSD or SerenityOS won't boot on there. Given Qualcomm's failures here, Nvidia is probably doing the right thing.

To each their own, but I don't recall Apple ever mainlining any of their drivers on Linux. You're rightfully angry on the laptop side of things, but Apple is much worse than Qualcomm when it comes to open source support for their phones.

Qualcomm probably shouldn't have promised Linux support in the first place. Everyone seems to love Apple's hardware even though you're practically stuck with macOS. Had Qualcomm just stuck to Windows-only, they would've probably received a much better reception by the tech press.

Some distros still need extracting Qualcomm firmware from Windows to get Linux to work properly. Audio remains a challenge, like x86 Linux decades ago. Apparently camera stuff works these days but produces images of subpar quality.

These issues also occur on normal Linux. My experience with my Lenovo+Intel laptop was that it took three months after release for the firmware to work properly (and the Nvidia drivers took much longer, but that's my fault for buying something containing Nvidia hardware). Intel managed to do what Qualcomm did in months rather than years.

I hope Qualcomm finally sorts this shit out, I really do, but with the prices of computers these days, I'm going to need to see quite the discount before I'll consider buying anything with a Snapdragon.

Platforms like Stripe where anyone can sign up at any time drive up prices because the amount of low-profit companies needs to be offset by the companies making more. Great for small startups but a bad deal for major companies.

Stripe has also been criticised for forcing growing companies into enterprise plans the moment they hit certain growth numbers. That's one way to keep the business profitable, but it's not necessary if you only take on businesses that are already profitable enough dedicate a sales team onto.