paru presents all pkgbuild diffs to you before installing, that's what I use to read them.
I usually only use AUR to install trusted pre-compiled binary packages, the scripts are very simple and the only thing that should ever change is the url and the sha256
Yea, paru makes it really easy, i noticed the diffs are a little easier/different versus yay. Not sure though if it's a config setting, haven't figured out the details yet.
Also paru shows you coloured code syntax if you have `bat` installed, i think.
Disarmament failed though? Global zero initiatives for nuclear weapons stalled out exactly because the risk of someone else cheating is too great. If everyone gets rid of their nuclear weapons and then someone cheats and creates them in secret they can use their nuclear weapons to prevent anyone else from catching up.
I grew up in a suburb like yours. I'm raising my kids in a suburb that's by and large the same.
The biggest difference, imo, is the number of families.
I lived on a small street with a cul-de-sac. Maybe 35 houses or so. At least half had kids aged 0-15.
I now live on a street about the same size with my kids. There is one house with ~7-10 year olds, two houses with 3-5, one house with a couple of teens, one house with a baby.
Nothing else really matters, you can't expect kid communities to self generate at these densities.
This is my current experience, too. There are a lot of "empty nest" houses on my street. Wouldn't it figure that those people are all upset about the apartments that are being built in the neighborhood which are all being scooped up by young families ...
Asking because I’ve seen the same dynamic in multiple subdivisions over several decades. I have very little love for subdivisions and the suburban built environment, but I wonder how many vocal urbanists’ opinions are colored because they experienced the aging of a neighborhood’s inaugural population. If you look at the neighborhood again in 50 years maybe it will have a healthier age variance.
Because the FTC has been defanged, and it was the main body preventing this sort of thing. Along with the CFPB for financial products (I don’t think insurance qualifies though.)
Because the problem space is basically infinite. If a person is working on a problem, its probably interesting to at least one person. Randomly walking through the problem space might be interesting, but I don't know how the signal will fare against other humans.
No, it is not. bcachefs needs to have all the code for error recover in the kernel as it needs to be available when a storage device fails in any of a myriad of ways.
Maintaining a piece of code that needs to run in both user space and the kernel is messy and time consuming. You end up running into issues where dependencies require the porting of gobs of infrastructure from the kernel into userspace. That's easy for some thing, very hard for others. There's a better place to spend those resource: by stabilizing bcachefs in the kernel where it belongs.
Other people have tried and failed at this before, and I'm sure that someone will try the same thing again in the future and relearn the same lesson. I know as business requirements for a former employer resulted in such a beast. Other people thought they could just run their userspace code in the kernel, but they didn't know about limits on kernel stack size, they didn't know about contexts where blocking vs non-blocking behaviour is required or how that interacted with softirqs. Please, just don't do this or advocate for it.
I don’t really see how it’s different than how you’d setup someone really junior to have a playground of sorts.
It’s not exactly a groundbreaking line of reasoning that leads one to the conclusion of “I shouldn’t let this non-deterministic system access production servers.”
Now, setting up an LLM so that they can iterate without a human in the loop is a learned skill, but not a huge one.
Is there a reason all workspace accounts need a project ID? We pay for gemini pro for our workspace accounts but we don't use GCP or have a project ID otherwise.
The reason is that billing is separate, via the paid tier of the API. Just a few minutes ago, I was able to test Gemini CLI using a Workspace account after setting up a project in the free tier of the API. However, that seems to have been a bug on their end, because I now get 403 errors (Forbidden) with that configuration. The remaining options are either to set up billing for the API or use a non-Workspace Google account.
I usually only use AUR to install trusted pre-compiled binary packages, the scripts are very simple and the only thing that should ever change is the url and the sha256
reply