Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Kola said:
That might have been true 20 years ago. Name 1 task for which there's no better alternative than Emacs currently.
Click to expand...
It's my window to my computers. What do I care what other people do.
unaboomer said:
Red Hat
Click to expand...
Red Hat wants to turn Linux userland into a Windows clone with support contracts and all that this entails. They want *consumers* to use "their" operating system. You're not supposed to think critically. You're just supposed to shut your mouth and accept whatever the corporate overlords deem "objectively correct". IBM comes from the same corner. They've already been like this since at least the 80s. The only difference now is that people are whittled down enough to actually accept this absolute bullshit.
CNerd Prog said:
Why do many projects call themselves an OS when they only do packages? NixOS, Guix?
Click to expand...
They like feeling important. Distro maintainers are the tranny jannies of the linux world. That's also why these "which linux distro is best" discussions are so asinine. It's all the same stuff. The best distros give you the most freedom and get out of your way otherwise.
 
  • Agree
  • Like
Reactions: Spot 'em Slot 'em, CEO of Gay, Willi Tokarev and 9 others
AmpleApricots said:
IBM comes from the same corner. They've already been like this since at least the 80s.
Click to expand...
100% correct

Red Hat assured the FOSS userbase that the acquisition (merger? whatever) by IBM would be "totally transparent" and would have no impact on RHEL or its derivative projects...

Within a year, they rebranded CentOS as CentOS (Piss) Stream to smoke out anyone who was using CentOS in a production environment. Despite their promise that it would be basically just a superficial change in management, it broke A LOT of shit. This forced firms who were freeloading off CentOS proper to either run outdated software for an indeterminate amount of time while the FOSS side of the RH community regrouped, or roll over to (paid) RHEL subscriptions to receive security updates while maintaining compatibility with the software they were running prior to the Shake Down. Many MIC/glownigger entities chose the latter because they were/are contractually obligated to remediate security vulnerabilities within a certain time.
 
  • Informative
  • Like
Reactions: HarblMcDavid, Wright, Dr. Sexbot and 6 others
unaboomer said:
100% correct

Red Hat assured the FOSS userbase that the acquisition (merger? whatever) by IBM would be "totally transparent" and would have no impact on RHEL or its derivative projects...

Within a year, they rebranded CentOS as CentOS (Piss) Stream to smoke out anyone who was using CentOS in a production environment. Despite their promise that it would be basically just a superficial change in management, it broke A LOT of shit. This forced firms who were freeloading off CentOS proper to either run outdated software for an indeterminate amount of time while the FOSS side of the RH community regrouped, or roll over to (paid) RHEL subscriptions to receive security updates while maintaining compatibility with the software they were running prior to the Shake Down. Many MIC/glownigger entities chose the latter because they were/are contractually obligated to remediate security vulnerabilities within a certain time.
Click to expand...
Then once other companies switched to OSes based on the 'Open Source' released source RPMs from RedHat they then closed that hole and license restricted them to customers which made CentOS the only official SRPMs that releases like Rocky could use. Which led to an unholy alliance between SUSE, Oracle and others.
 
  • Informative
  • Like
Reactions: Wright, Blackhole, 306h4Ge5eJUJ and 3 others
Eternal Spirit of Light said:
I should have clarified that I'm talking about Arch-based distros since they're so autistic.
Click to expand...
Why does everyone keep saying this? What is "autistic" about Arch-based distros? It is really no different from any other distribution. The only real differences are a terminal-based installer in the original Arch, and starting with barebones packages. Literally `$ sudo pacman -S xfce4 lightdm` and `$ systemctl enable lightdm` and you have just done the hardest thing to do on a new Arch install. With the pacman repositories and the AUR, you'll never miss a package again. Get yourself a GUI frontend that supports the AUR and you won't need to touch the terminal for them. Everyone who tells you that "arch is unstable", "arch is rolling", "arch updates will break everything", or that "arch is complicated" is a huge fucking retard who doesn't fucking know shit of what they're talking about.
So honestly, tell me how the fuck Arch-based distros are more autistic than something like Ubuntu?
bort420 said:
all the people bitching about systemd have yet to come up with something good enough to replace it

systemd is complicated but better than sysvinit/openrc so 🤷‍♂️

also most of the bloat in systemd is other projects being developed under the systemd umbrella. it's a brand now
Click to expand...
Obvious bait. No one is this retarded. I fucking hate OpenRC but I damn well know Systemd isn't any better than it. Dinit is my go-to. I run this shit everywhere, even on servers, and it has never failed me. Literally the perfect init system.
 
  • Dumb
  • Thunk-Provoking
  • Agree
Reactions: Spot 'em Slot 'em, ellroy, Kyangyenki and 5 others
The whole "Arch Linux is too autistic for me" is weird too because you can totally run multiple distros at the same time via bottles or containers. For example, I use Alpine Linux with an Arch Linux container to run games, and get software not available on Alpine. You can mix, and match, stuff for your use cases. Using Arch doesn't lock you into a single distro. Maybe you want a stable distro, but something bleeding edge for games? You could totally run Debian with an Arch Linux container for your steam or wine stuff. FreeBSD also has a feature to do this called "jails", but I'm not too experienced with it.
 
  • Autistic
  • Horrifying
  • Lunacy
Reactions: Kyangyenki, Samuel Fuller, Blackhole and 3 others
Frederica Bernkastel said:
The only thing I like about Systemd is Systemd-boot because it's simpler than grub, and you can use it without Systemd. That's one of problems with systemd. It's not modular like that.
Click to expand...
systemd-resolved can be used like that too, i think. it used to be pretty dogshit but i've been using it for a few months now without issue.
 
  • Informative
  • Horrifying
Reactions: Heliantheae, Marvin and Frederica Bernkastel
Max Free said:
Isn't the whole reason containerization was invented because everybody gave up on that exact requirement?
Click to expand...
No, not everything can be containerized. I get warnings when updating docker that certain options from the kernel I run is missing, older glibc may fail. I don't really run old versions of docker images, but I imagine if I did, it might stop working a decade later unless I rebuild everything.

Edit:
Looking Glass said:
Did you know that mpd will halt the shutdown process until the currently playing track finishes? That's usually what my unreasonably long timeouts are.

Edit in response to edit:

Dbus is an abomination in nearly every aspect and should be destroyed. I am very happy kdbus was never merged.
Not only does dbus's system/session bus concept force arbitrary layers of services that don't play nice in any kind of nested service scenario, but the under-typing of the system, and design around glib's variant type makes it such a pain to deal with from any language or library.
Click to expand...
So much this, I found out one day none of my chromium based browsers would start, they all mysteriously crash, everything else would work fine. Turns out dbus failed to start properly because of some broken configuration, chrome and friends just can't run without calling something over it.

The same with nested services, when I tried to run a supervised process directly off PAM that required dbus. "No problem, I'll just run it in my own isolated dbus session" I thought. Turns out some dbus service won't even start properly unless X DISPLAY is already running, even if dbus itself starts fine.
 
Last edited:
  • Like
Reactions: UERISIMILITUDO
NortelNutworks said:
Lots of us are sick of it making shutdowns and reboots take indeterminately long for no apparent reason for over a decade.
Click to expand...
That sounds more like a problem with the program that can't quit cleanly when told to. I don't see a convincing argument how this is supposed to be systemd's fault. And if that's its worst flaw, then it sure as hell is better than alternatives.
 
  • Dumb
  • Autistic
  • Dislike
Reactions: Cherenkovblue, NortelNutworks, Guy who lurks and 12 others
My main beef with systemd's retardation is how it replaces well known systems like cron, syslog and resolveconf with it's own, shittier methods of doing things, and when distro's all started deepthroating Poettering's dick as hard as possible they put in a bunch of clunky workarounds to keep the old configs working without really explaining shit which made it worse.
 
  • Agree
  • Like
  • Thunk-Provoking
Reactions: Spot 'em Slot 'em, CEO of Gay, Smith Banquod and 9 others
Hexadecimal Machine said:
Everyone who tells you that "arch is unstable", "arch is rolling", "arch updates will break everything", or that "arch is complicated" is a huge fucking retard who doesn't fucking know shit of what they're talking about.
Click to expand...
My personal theory is that people think Arch is unstable and breaks things because they're running on old and worn out hardware. Anytime Arch has failed on me it's been because a piece of hardware is actually at fault and Arch's nature as a rapidly updating Linux system is what makes those hardware errors unmanageable. If you have a bad RAM sector it could conceivably fly under the radar for a long time causing minor errors here and there... unless that sector is used while you're updating your Kernel in which case more things start exploding.
 
  • Thunk-Provoking
Reactions: Guy who lurks and 306h4Ge5eJUJ
You must log in or register to reply here.
Back