Team Monsanto’s Lead Junior Red Dawn war re-enactor/co-ordinator for Anniston, Alabama
Reminds me of the clip of Billy Bob in land man: “Do you know how many resources go into building a frickin windmill?!”
Yeah, not that many, dumbass.
We can recycle batteries, we just don’t because they last way longer than expected and almost no one has needed to replace them yet. We aren’t just mining this stuff and then setting it on fire like we do with oil.
EVs are better experience in every way, unless you live outside a major population center where charging stations are spotty, deal with freezing weather a lot (some models are better than others in this regard), or you don’t have a place to plug the car in and let it charge overnight.
You might get unlucky with the battery or some esoteric cpu or software bullshit, but that kind of thing is a problem with every car and you can probably get it fixed for free. If the model was discontinued it might be a headache to get it fixed.
Just don’t buy used unless you can test the condition of the battery. Battery’s were a problem on early model nissan leafs due to poor thermal management, but for the most part every EV car battery is lasting way longer than expected and are slow to degrade. If there wasn’t a manufacturing flaw, and the person kept the car charged when not in use, and sensors are saying there’s not faulty cell or something, it’s probably good to go.
He should of spelled it Vverevvulf
According to this post, once these projects move to bootc, they are going to get rid of layering and allow you to just dnf install what you need.
Recent discussions upstream has consolidated around doing things the Ublue way. Pulling a base image from an upstream registry and using containerfiles to define a system locally. No custom scripts and unit files. No GitHub. Just writing custom changes to a containerfile and having them automatically apply on reboot. Running dnf install @virtualization would add the following line to the containerfile in the background:
RUN dnf install -y @virtualization
The powerful thing about build time container image layers like this is that you can do deep customizations like switching out the kernel, changing the login manager, use your own custom boot screen, or redistribute your build by pushing it to a public/private container registry or as the Ublue team shown use container based ci/cd workflows for automated vulnerability scanning against public databases like NVD and CVE.
Seems like it will get rid of a lot of pain points.
smdh
Hornet is a Mary sue designed to emasculate bug men.
Currently what I’m using and I’m never going back to a regular distro.
I’m using a regular stable distro, running as a small server on a spare machine, update and break my docker containers. What a drag.