The Linux Thread - The Autist's OS of Choice

Everything that guy takes over should be required by law to have a "from the minds behind Paint 3D" on the splash screen
Oh, I always forget that this guy was involved with Paint 3D, probably one of the most useless things shoved into every bloated Windows install. Also where does he get off on making fun of some random small tuber's teeth?



Reminder, the guy who said that looks like this:
1759565376222.png
 
Is MacOS not-Gnome? Then it is better than Gnome. Gnome is gratuitously bad at everything.
I have never agreed to a piece of written text more than this lol

The shittification of Gnome is something else, like this shit from the article, from the app store app:
1759579483389.png
The gnome trannies pretend as if sandboxing actually exists on desktop Linux at all lol. Running someone's code on your computer always means you can get your crypto keys stolen, no flatpak and not even ayyland will save you.
 

The plans for another FOSS project on Linux probably getting ruined/GNOME'd just dropped. I remember people in this thread suggesting that this dude is responsible for Audacity being fucked, I guess it wasn't a joke. Dude is pissed in the beginning about people criticizing a dev build. But aside from the logo change it could be good, idk I am just too cynical about shit like this now. All I know is that Audacity has just gotten worse and worse for me personally performance wise on Linux at least. IDK how it functions on macOS which seems like the main system they are making it for nowadays.
I actually really like the way it looks. The new logo sucks, but most modern logos do, so that's to be expected. If the performance is good, the change would be more than welcome, at least for me.
 

The plans for another FOSS project on Linux probably getting ruined/GNOME'd just dropped. I remember people in this thread suggesting that this dude is responsible for Audacity being fucked, I guess it wasn't a joke. Dude is pissed in the beginning about people criticizing a dev build. But aside from the logo change it could be good, idk I am just too cynical about shit like this now. All I know is that Audacity has just gotten worse and worse for me personally performance wise on Linux at least. IDK how it functions on macOS which seems like the main system they are making it for nowadays.
Wow they completely raped it to death, can't wait for the future of Audacity to be an electron webapp written in TypeScript!!!!!!!!

sneedacity when?
https://github.com/Sneeds-Feed-and-Seed/sneedacity rvtvrn....
 
You mean IBM?
No.

IBM bought Red Hat in 2019, long after systemd was adopted and reached a stable state for distros to use and not consider abandoning it after the purchase. Poettering was playing with the idea of systemd as early 2010. In 2011 Fedora used systemd by default. I can't find the interview but Poettering claimed his superiors at Red Hat weren't on board with creating a new init system and he claimed that they were willing to let Canonical develop it. I don't buy this for a second. I'm not going to assume bad faith on Poettering's part and say he lied about what really happened but I willing to bet he didn't understand that conversation he had. There is no way Red Hat, a public traded company at the time, was just going abandon potential business growth in favor of a competitor, as Canonical sells support contracts too and Ubuntu server was popular at the time. If anything I think Red Hat didn't want him fucking up like he did with PulseAudio. Canonical was working on Upstart at the time but couldn't get it off the ground and Upstart was abandoned in 2014, eight years after it's first release. There is no way Red Hat would of looked at that and been like "we can't compete, lets not try." IBM bought Red Hat because they knew the position Red Hat was in concerning Linux, what they didn't realize is there is only so much money in support contracts, hence their fuckery with the NDAs.

I've been very critical of systemd and it feel disingenuous because I wouldn't mind it if there wasn't attempts to constantly absorb more processes and utilities under systemd. Now apparently systemd is experimenting getting Rust in it and all the baggage that will come with that decision both technical and community. If systemd was just launchd but for Linux, I think I would happily use it but now its Poettering trying to create Windows out of Linux. Circling back to canonical, one of the worse integrations of systemd I have seen is from Ubuntu because by default, systemd is allow to update itself on boot and you can't use apt until it concludes.

I should start experimenting with Gentoo and Artix for when the time systemd becomes too much.
 
IBM bought Red Hat in 2019,
Shhhhhh

Circling back to canonical, one of the worse integrations of systemd I have seen is from Ubuntu because by default, systemd is allow to update itself on boot and you can't use apt until it concludes
Horrifying
I should start experimenting with Gentoo and Artix for when the time systemd becomes too much.
Do it Gentoo stronk (at least if you don't mind updating at night before going to sleep or before you go to work during the day. To avoid running builds in the background for big updates while doing other stuff, most updates take about 2-5 minutes though).
 
It's not open source, but it is a pretty nice audio editor. ocenaudio might as well be a good alternative for nu-Audacity given how bloated and overengineered it has gotten after the buyout.
Personally, I think this works as a great modern audacity alternative

The plans for another FOSS project on Linux probably getting ruined/GNOME'd just dropped. I remember people in this thread suggesting that this dude is responsible for Audacity being fucked, I guess it wasn't a joke. Dude is pissed in the beginning about people criticizing a dev build. But aside from the logo change it could be good, idk I am just too cynical about shit like this now. All I know is that Audacity has just gotten worse and worse for me personally performance wise on Linux at least. IDK how it functions on macOS which seems like the main system they are making it for nowadays.
This video seems okay (logo sucks) but as a rule of thumb I never trust a developer or a project that makes a PR "here's how it works" meta professionally edited youtube video over actually just working on the software, I've seen so many game devs that do this with projects that end up vastly overhyped and bloated with suggestions from people outside of the scope of their audience. You have people complaining about Silent Hill F discourse in the comments of this so you know this video is especially pozzed. Audacity should have never gotten to the point of a video like this being needed really.
 
This video seems okay (logo sucks) but as a rule of thumb I never trust a developer or a project that makes a PR "here's how it works" meta professionally edited youtube video over actually just working on the software
That's why I am cautious because the application changes seem fine on the surface, but the video itself and esp this dude's attitude to any criticism even of a dev build is what makes me think shit is going to stink. I am not too worried since we do have the Tenacity fork to fall back on.
 
I have never agreed to a piece of written text more than this lol

The shittification of Gnome is something else, like this shit from the article, from the app store app:
View attachment 7996971
The gnome trannies pretend as if sandboxing actually exists on desktop Linux at all lol. Running someone's code on your computer always means you can get your crypto keys stolen, no flatpak and not even ayyland will save you.
Sandboxing works fine. That's what VMs are for. Oh, Flatpak, let me laugh some more.
 
I should start experimenting with Gentoo and Artix for when the time systemd becomes too much.
Even with Gentoo or Artix, you will still use parts of systemd on non-systemd inits like udev. There is a way to remove it, but it's often not worth the effort. In any case, if you do switch, dinit would be the easiest to use because it uses a similar service management syntax.
 
Sandboxing works fine. That's what VMs are for. Oh, Flatpak, let me laugh some more.
Yeah. there are decent sandboxing options on linux. A lot of people don't bother to take advantage of them though, I feel like half the people don't even know what the sandboxing options are on linux. But flatpak is shit for sandboxing. From what I recall, unless they fixed it, they even break browsers own sandboxing, because they won't allow suid in bubblewrap, so it possibly hurts security. You are better off doing your own sandboxing, and allowing the browser to use it's normal sandbox, within your own sandbox, at least until none of the browsers are using suid sandboxing anymore. At least that's my opinion.

Then there are also things like apparmor, or selinux. With those, you can have a system so locked down, it literally can't function anymore if you wanted. That's obviously not practical, but you can have a very secure system is my point. Obviously it will only help so much, if somehow something makes it past it, to the firmware, or something. Like some kind of 3 letter agency type exploit, with a backdoor. But in that case, there isn't much you can do anyway.
 
I should start experimenting with Gentoo and Artix for when the time systemd becomes too much.
Even with Gentoo or Artix, you will still use parts of systemd on non-systemd inits like udev. There is a way to remove it, but it's often not worth the effort. In any case, if you do switch, dinit would be the easiest to use because it uses a similar service management syntax.
Right now, the most purist no-systemd distro is likely antiX. Its a Debian fork without any systemd elements whatsoever, no udev, no elogind, nothing, all those functionalities are replaced by their own in-house scripts. I use it for my storage box, its pretty good.
 
Yeah. there are decent sandboxing options on linux.
chroot jails have been a thing since forever.
Then there are also things like apparmor, or selinux. With those, you can have a system so locked down, it literally can't function anymore if you wanted.
We would disable selinux on RHEL6 because of how overly restrictive it would be. Unless you were running very simple applications, it would catch lots of things and block them, which required you to go through and watch all of the sealerts and add custom rules for the most minor of shit. So it just became a blanket disable until RHEL7 came out, which actually had a very sane implementation out of the box. Still been bit in the ass by it, but over relatively minor things that a quick relabel/reset context fixed.
 
Back
Top Bottom