I do know it’s not completely literal

Are you trying to kink shame?

This is propaganda: […]

FTFY

They don’t hate them. They just want to cut all support for citizens to have more money available to finance more tax cuts for rich people.

But to do this you need to somehow convince the masses that money spend on them is a bad thing. For decades trickle-down fairy tales of how spending money on the already rich ones will help the economy and then be beneficial for all worked. But not anymore. So the next phase in desinforming gullible voters is much more dystopian and involves straight out brain-washing to decouple them from reality and make them believe that people actually helping them are evil and need to be fought.

Batteries losing more than 20-25% of their capacity in 150.000km had a defect in production already. You can find similiar numbers in any OEM’s warranty. So a non-defective battery will provide at least 80% of its capacity at 150.000km. The average car manages about 250.000km over their life-time of about 15 years (reference numbers from the US, so the most pessimistic view as barely anyone else in the world is matching those distances).

You are not completely wrong. Used batteries will be a problem… somewhere far down the road because electric vehicles are expected to easily manage 800.000km or more (less moving/wear parts).

But we are not there yet. The whole EV market isn’t old enough to have produced these long-lived vehicles and we are back at my original point. Today it’s not about battery degradation but about EVs not getting old fast enough to already have established a robust used market. In fact the first big batch of EVs on the used market is often not expected for another 2 years (see here for example, and that’s again rather new vehicles because of a loophole for leased cars in the EU).

In short: There isn’t a huge used EV market yet and (more importantly) the demand is stifled by battery degradation fairy tales not relevant (EVs old enough for this basically don’t exist yet) and political mismanagement subsidising new EVs.

With nuclear, you’ve got a raging anti-nuclear crowd.

No. With nuclear you have very real unmitigatable risks and very real insanely high costs. Which also don’t solve anything as nuclear production isn’t fitting demand fluctuations either, so you still need mass storage (or waste overproduction 90% of the time, combined with already insane costs).

The raging crowd is the pro-nuclear cult on social media that ignores reality and sputters sci-fi fairy tales all day long in the name of their savior.

It’s obvious for everyone with basic logic skills.

But that doesn’t mean we can’t try and twist the fact for anti-EV propaganda. Because it’s really, really, really important we keep burning oil… if you are someone selling oil and have the money to spread bullshit for personal gains that is.

What do you think the average 10 year old car has done to that point? Battery degradation is hugely overrated and stories are based on tech already left behind.

The actual problem for the used car market is the opposite: EVs live much longer than traditional cars and thus don’t lose their worth that rapidly, while on the other hand new cars still see a fast development cycle while also getting cheaper.

So no, it’s not a problem of used EVs per se and that their expensive batteries are allegedly dying. It’s the fact that a new EV just a couple of years later is ahead 1-2 generations and also cheaper.

ARM is shit at hardware discovery in general. So no, chromebooks don’t need a special distro. They however need a kernel adapted to the specific hardware, often down to the model (that’s also the reason Android updates take so long on phones and there is very time limited support… there’s always someone needed to adapt new updates to the specific hardware for each device, so they don’t bother for anything but their latest products).

So what humans have done for millenia in the form of furs, leather and bone?

Bigotry is illogical

Yet this isn’t even bigotry. It’s straight out xenophobia and hatred. The sanctimonious bullshit is just a fig leaf…

Decryption isn’t a problem if you use the systemd hooks when creating your initrams. They try to decrypt every given luks volume with the first key provided and only ask for additional keys if that fails.

I have 3 disks in a btrfs raid setup, 4 partitions (1 for the raid setup on each, plus a swap partition on the biggest disk), all encrypted with the same password.

No script needed, just add rd.luks.name=<UUID1>=cryptroot1 rd.luks.name=<UUID2>=cryptroot2 rd.luks.name=<UUID3>=cryptroot3 rd.luks.name=<UUID4>=cryptswap to your kernel parameters and unlock all 4 with one password at boot.

It has lots of small issues that add up to a frustrating experience for mainstream users.

And 90%⁽¹⁾ those are out of Linux’ actual resposibility because they are caused by third parties screwing up… sometimes even intentional (from companies producing lackluster drivers only having a fix cobbled together for Windows specifically -looking at Realtek networking for example- to ones actually going out of their way to block Linux (MS FUD included…).

⁽¹⁾ The other 10% exist on Windows or Mac also, but people just accept them because they are used to not having a chance to change it. Seriously the amount of obscure regedits or third party tools usually surpass the number of linux issues fixed by editing an easy to read txt file.

The majority of “Linux issues” is created intentionally. It’s often not enough to not support Linux officially (even if there would be no additional work involved anyway) and let players figure out problems on their own. A lot of studios, publishers and developers actually go out of their way and actively invest time to block Linux.

So nothing will obviously change. Windows could run on a fully compatible Linux kernel tomorrow and games would still check for Linux to artificially create issues.

Actual wolf packs are a family. One pair of adults plus their children. Until those are old enough, then they leave and search for a partner and own territory.

All the stuff you read about pack alphas, all the sociological pseudo-science about alpha behavior derived from it… that’s all based on a one bullshit study about a large group of wolves artificially intoduced to a new area, that in no way behaved like wolves naturally do.

Basically the equivalent of putting a few dozen teen-age boys on an isolated island then studying their behavior to understand human society.

Let me google that for you: Quark

Car-brains don’t do standard logic, only car-logic…

So this is what happens when a Fiat Multipla develops into its final form in all its glorious ugliness…

Depends on the intended effect… I personally see this as just one single piece in a big wave of equally dilettante articles used to convey one message to the caual reader: that 3d printing is bad, dangerous and needs to be regulated.

And we all know who’s willing to pay money to push that story…

There is a difference here.

Unlocking home later in the boot process is not a problem, so the you can indeed have a keyfile on your root and get your home unlocked and mounted after root is done.

Swap however needs to be available early, at least if you want to use it for hibernation.

This would -at least as far as I understand it- limit your swap’s functionality for hibernation etc. Because there your swap needs to be available early. You can still do it in theory, but the key file then would need to be included in you initrams, which kind of defeats the purpose.

There is however a much more easier option: either use LVM on luks (so the volume is decrypted with the password and then contains both, root and swap) or just use the same password for root and swap while switching over to the systemd hooks (as those encryption hooks try unlokcing everything with the first provided password by default, and only ask for additional password if this fails).

EDIT: Seeing that you crossposted this from an archlinux-specific community: You can find the guide here. It’s for using a fully enrcypted system with grub as bootloader, but the details (in 8.3 and 8.4) are true for all boot methods. Replace the busybox hooks with their systemd equivalents (in minitcpio.conf for archlinux but again this isn’t limited to that init system), then add “rd.luks.name=<your swap’s uuid=swap” to your kernel parameters and also replace the “cryptdevice=UUID=<your root’s uuid>:root” that should already be there for an encrypted system (that’s the syntax for the busybox hook) with “rd.luks.name=<your root’s uuid>=root”. On startup you will be asked for your password as usual, but then both root and swap will be decrypted with it (PS: the sd-encrypt hook only tries this once… so if you screw up and misstype your password on the first try, you will then have to type it again two times, once for root, once for swap…)