5,217 karma · joined May 14, 2020
The bar was a president that doesn't start pointless wars. That's a low bar. Biden cleared said low bar by not starting pointless wars.
And of course when I look up the problem, the threads I land on don't point me to a thing to toggle in the UI. No, instead one of them directs me to create a config file for pipewire while another says the remove a specific package entirely. And they're not presented as a set of clear steps to follow, so good luck to your average person trying to fix the problem for themselves.
I just don't get it myself. When users complain about the software I've released, I look to see if there's reasonable changes I can make to alleviate their issues.
They can also waste a lot of time if you end up over-reliant on them, but that's where experience with LLMs comes in. The nature of them means it's not an exact science, but you get a feel for how to best apply them.
Plus, updates aren't the only thing that require reboots. Various config changes will need a reboot or at least require you to log out and back in. Even just adding your user to a group needs you to end your session for the change to apply.
But the really nice thing about the concept of treating a PC and console as the same platform is that you don't have to worry about why people might prefer to go the route of buying the console. You can go with a regular gaming PC if that's what you prefer and your library will have all the same options.
Also it's helpful to log before operations rather than after because if a step gets stuck it's possible to know what it's stuck on.
And it's not like I don't care about performance. If I see a small query taking more than a fraction of a second when testing in SSMS or If I see a larger query taking more than a few seconds I will dig into the query plan and try to make changes to improve it. For code that I took from testing in SSMS and moved into a Dapper query, I wouldn't have noticed performance issues from that move if the slowdown was never particularly large.
(e) (1) “Covered application store” means a publicly available internet website, software application, online service, or platform that distributes and facilitates the download of applications from third-party developers to users of a computer, a mobile device, or any other general purpose computing that can access a covered application store or can download an application.
Also, where does anything in the CA bill mandate age verification? It's saying the OS needs to prompt for age bracket info and allow the third party apps to query that. That is far different from verification.
That's exactly what I was thinking when I read that line. And there's nothing necessarily wrong with using AI to help decipher large legal documents, just be honest about it.
"It certainly sounds like something an app from a big Chinese company might do"
Doesn't mean I want to blindly trust a random source about it though.