But that would imply that Python is faster than the one in this comic!
This can't be C++. Not enough stacks of unneeded template names, and the function names are not mangled beyond recognition.
Oh if only Proton could learn this power!
endless feed
to fight algorithm addiction
endless
feed
to fight algorithm addiction
Uuuuuh that's not the way to fight an addiction, right? Who is this person working for, exactly?
Okay lemme understand it.
"Terrorism" is defined as using violent means to scare or suppress the population.
But what he did made the population happy.
So... shouldn't it be considered that he provided a public service?
This definitively was not in my 2024 Bingo card:
Republicans masking
Well, what’s stopping someone else from adopting TomHanks@Lemm.ee?
There's over 1400 people solely in the US named Tom Hanks. Tom Hanks The Celebrity does not get patent rights or trademarks or copyrights on the name.
Wanna know which is the Tom Hanks The Celebrity? Check if their profile is authenticated against their personal website, à-la-Mastodon.
What I'm hearing here is
Proposal to add current Fediverse symbol to Unicode
Storm in a teacup, as tends to be the norm on the internet.
Not only this is nothing new and nothing unexpected to happen in Sid of all places, but it's also something that helps bring keepassxc more in line with packaging guidelines on Debian. They already have lots of packages, both of the mutually-exclusive kind and of the complementary kind, with "foo-full", "foo-minimal", "foo-data" etc naming. p7zip and nginx of all things are quite interesting examples.
Plus, the author of the post sensationalizes the title to brigade the issue.
All that said:
- If the maintainer wishes to do this, "only" having two packages is a half-assed measure and that causes more issues in the long term. I'd expect three packages:
keepassxc-minimal
,keepassxc-full
and the retained namekeepassxc
as a virtual package name. - Furthermore, a direct upgrade path should go from (previous)
keepassxc
to (proposed)keepassxc-full
. - I don't know enough of KeePassXC to know if something like
keepassxc-data
would be needed. Are there potential cases where one would want to switch between "-full" and "-minimal" or viceversa without the system seeing a software uninstallation in the meantime? - The "crap" rationale is definitively something we all can do without, but given how people tend to brigade developers who try to do things, I can completely understand and support raising shields and looking defensive because some damage is already going to be done.
- Most responses are right in that the right place to discuss this is in the opened Debian bug report. The entire point is to see Debian (not KeepassXC) handle this before things get to Next Stable.
Germany never really stopped being a nazi country, did it?
As much as Germany denies it, it has been proven in the last 10 or so years that they really loved their nazi days. France seems to also love having been under nazi occupation too, and they seem to have a similar anti-environmentalist attitude.
Problems Linux itself has to overcome? Maybe two or three.
Problems that are mistakenly attributed to Linux but that are actually for manufacturers, sellers and provisioners to take responsibility for and overcome? A good lot.