Much as I'd have enjoyed seeing it, it would have greatly hindered adoption when the general public started finding out about furries in the early 2000s and would have made Linux look like a toy not for serious use.
Poor Mauro: they weren’t good at what they loved, they blamed others for their failings, and their community leader was nuts.
Jokes aside, we’ve already got toxic right there. Linus isn’t right, but someone like that would be fired with good cause. It’s one thing to make a mistake, it’s quite another to blame your co-workers for your own shoddy work.
I wonder if the guys here who are moaning like the snowflakes they are about Linus’ way of conveying the message (not the message itself) are from the US? I sometimes really wonder about the US mindset. The boss is critisizing you justifyably but in an inadequate tone? Hell breaks lose. But as an employee insisting on healthcare, an adequate number of days on paid time off, unionazing or at least have an able workers’ representation? Nah, that’s unheard of.
How about having some priorities? Grow a pair and chose your battles more wisely. The boss criticizes you? If he’s right, own up to your mistakes. Want some rights you are actually entitled to? Yeah, that’s what you fight for.
Don’t allow your boss to speak to you like that, unionize, and fight for your workers rights - including the right for dignity and respect, listed in the Universal Declaration of Human Rights, but also for higher pay and better working conditions.
After twenty plus years of watching LKML and Linus’s behavior in general, I have to concur with you. Reading a lot of the ‘linus is an asshole’ threads, there’s generally a clear runup towards an outburst.
Just recently he called some developers out because it seemed evident they weren’t testing their patchsets on bare metal. So it’s not just code that gets called out, it’s also development methods that end up causing upstream pain.
So… Basically just tangentially linux-related. Also, Xenia wasn’t the original mascot. Tux came first, and Xenia was proposed as an alternative, but never took off.
You‘re not wrong. I left firefox since you can’t say anything critical about firefox without being downvoted to hell even if it is just trying to improve it.
Wonderful how the people spoiling irl groups also spoil online groups.
I have no idea if it is censorship but the amount of jerks throwing shit at you for saying {insert critical question} is insane. I‘m not talking about „did you know mozilla sells kid slaves?“ idiocy but things like „I don’t like that google is the main financial contributor“ stuff.
A few days back someone posted this article on the firefox subreddit. It is a well written article with good points, but the hivemind ignored the content of the article and resorted to ad hominems and name calling because the author is a supposed right winger. It would not be surprising if the post was removed by now.
You’re just proving my point. I haven’t seen anyone point out anything wrong or misleading from that article. Only name calling and ad hominems. I do not care about the author. Why can’t you just focus on the contents of the article?
All he did was repeat shit that we’ve known for years in the most sensationalist way possible so he could get a fucking profit of a clickbait article.
He’s a “journalist”, wtf do you expect. This is his entire deal; repeat already well known shit, sprinkle in some sensational nonsense, do zero due diligence as a journalist and use the most clickbait title possible for profit.
I’m sorry, but his shit always reads like an AI wrote more than half of it, and when he won’t even ask the people involved like he’s supposed to as a journalist, he’s bringing nothing new whatsoever, only speculation and sensationalism.
That’s all there is to it.
I especially see it a lot around things I have deep interests in that a lot of people have light knowledge on, so it’s probably the Dunning Krueger effect rearing its ugly head :(
I guess the main way to combat this is to join nicher communities, but that’s not really possible on Lemmy right now because of its small size :/
One does not simply break userspace. You’ll receive more than just angry bug reports. There are restless maintainers who will not sleep. And the great corporations are ever watchful.
Ideally, you should use Pamac (if you’re doing CLI), not Pacman, to update Manjaro. Haven’t used Manjaro in a while, but this is gospel most of the time.
Seriously. I used Manjaro for a short period about 5 or 6 years ago but ran into so many issues with it. Vanilla Arch on the other hand is very forgiving in my experience. I have a second desktop PC with Arch installed and I only update that machine once every couple of months when I actually need to use it. In my four years of doing that I never had an update break my system.
I’ve used and come back to Arch for nearly 8 years now and Manjaro has always been a broken distribution and genuinely gives Arch a bad rep.
Arch has always been a very stable daily driver for me, never breaking and never having issues with it. I’m always confused on what people are doing when they have issues with their entire distro breaking, especially since you pick all your packages and such anyways.
I’ve had a few breaking changes in 10 years of dailying Arch across multiple devices.
Most egregiously one time a PAM update included a new PAM config… which got applied as .pacnew, but the new PAM config was critical and I could not login with a cryptic error message.
That probably took me a solid hour to figure out, because config file conflicts is probably pacman’s weakest point. At least apt starts conflict resolution by default.
I don’t think in this specific case it does, though. I had similar problems with a completely different distribution. I’m convinced that it’s an upstream Qt or KDE issue where broken caches or changed cache formats don’t get automatically invalidated and rebuild. In the case I vividly remember some lower level graphics library was updated and everything seemed to run fine but for some (and only some) users it resulted in Qt or some KDE component not being able to parse the cache any longer. After some research (under Gnome) I wrote a small script that quit Plasma and KWin, deleted all the caches (icon, font, …) and then launched KWin and Plasma again. Worked fine and came handy on a couple of further occasions.
linuxmemes
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.