But not the vibration. Of buzzing. Like the “gravel”-y type testosterone vibration.

At least it has the vibration.

WSL, Deepin for an hour, and then endeavourOS (easy Arch) ever since

That’s not what the article says at all. They interviewed the maintainer and he explicitly said it was to not hurt CodeWeavers.

deleted by creator

You do realize he has said he did this out of personal admiration and hope for the Wine project’s funding? If he had cowered he would not have lied. As seen in what he said when a previous project he worked for, Ryujinx, was shut down. No reason to believe there was any bullying.

Cowardice?

Said paid app is CrossOver, which is pretty great actually. CrossOver contributes all modifications back to Wine while CrossOver the product is just a proprietary set of per-app environmental configurations.

Good thing there are community frontends.

If you want to run post-upgrade, you got to do it yourself.

That’s just wrong. Pacman has hooks, and easy hooks are one of the reasons Pacman is loved. In a normal weekly upgrade I see Pacman run over 30 hooks. I do not think simply not updating user-modified config files is just the bare minimum needed.

I think this boils down to Arch’s philosophy: the users should know their system, and when something could break things, don’t assume things and do it automatically; have the user do it instead. Thus when shipping config updates to a user who had already changed their config, Arch does not overwrite the configs and instead ships the updated vanilla config with a .pacnew suffix. The user is expected to review such pacnews, a process that’s just like normal git merge conflicts when you use the pacdiff tool.

Agreed. The normal pacman CLI does have a comparatively much higher learning curve though compared to e.g. APT. It’s not that hard to learn either but when you’re scrolling over a long-ass manpage, you do not immediately realize from the headers which whizz by in a flash that -S (alias for --sync) is for installing from repos, -Ss is for searching from repos, -S does not by itself “synchronize” with repos by pulling newest repo package metadata because well that’s not what we’re “synchronize”-ing with and you have to add the “y” flag, -Su (remember to add “y”!) is for upgrading all packages instead of -U (alias for --upgrade), and -U is for installing a local package. Compare that to the APT/dpkg system’s apt install, apt search, apt update, apt upgrade, and dpkg -i.

Admittedly APT does need one to get behind the fact that there are different commands and that “update” and “upgrade” are different, but that’s way less to remember (especially since apt is meant to be the interface for everything a user should do) compared to remembering pacman’s interesting definitions of database, query, sync, upgrade, and maybe files, while the only definition unlikely to be guessed with APT IIRC is update vs upgrade. You’re far more likely to need a pacman cheatsheet than an apt cheatsheet.

But in the end, let’s all love libalpm, and the actual code behind that pacman interface.

extra 4% tariff on aliased packages

how so lol

that’s yyyy-mm-dd

This. This is the way. Even if the APY is just 4% I get 40k free.

no the real verse is just fantasizing about having sex with some conservative anchor

https://undelete.pullpush.io/r/appers/comments/83j49o/new_conservative_rap_idea

@impudentmortal@lemmy.world @ZILtoid1991@lemmy.world @agamemnonymous@sh.itjust.works

deleted by creator

North America, of course! /j

Can’t Stop Me

Like Amanpour & Company and The Late Show with Stephen Colbert, though these admittedly do have a bit of difference. And The Daily Show is late-night.