Cuntflaps
kiwifarms.net
- Joined
- Apr 19, 2021
Pretty self-explanatory. Why do YOU hate Linux?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
*because I'm tardedIt sucks because you suck.
Unless you jumped into trying to use Arch Linux right off the bat. (and even then...), there's basically no excuse for not being able to figure stuff out if you can readI installed it when my windows went poop and I regretted it later because I was a dumbass and couldn't figure anything out. Had to get someone to reinstall Windows for me. It's embarrassing that I spend basically me entire life on computers but know fuck all about them
I was able to use the operating system I just couldn't play the games I wanted to like Halo and my MIC was a windows only mic.Unless you jumped into trying to use Arch Linux right off the bat. (and even then...), there's basically no excuse for not being able to figure stuff out if you can read
* My thoughts on systemd are kind of mixed, to be honest. In the before time, systemd wasn't as widely used and wasn't very stable. You were better off with distros that used more traditional init in my opinion. However, we now have excellent distros that use systemd by default, like Arch--and the distros that benefited from the simplicity of foregoing systemd (in my case more specifically Slackware and later Gentoo) are more or less obsolete in their own ways. However, I still have yet to spend any time learning the internals of systemd. And if something is wrong with a unit, for example, I might just be kind of fucked. Whereas back in the day, even a relatively frightening failure in bringing up a service or what have you could usually be fixed with a bit of shell scripting knowledge. But let's be honest: that's my fault, and every problem I've had since switching to a systemd-based distribution has been solved by configuration changes completely unrelated to systemd itself.No split between the base system and local.
The system-d fiasco.
Its users who write fsck for fuck.
The almost completely random standards/conventions for the locations of files.
I personally think systemd is a better init system for enterprise and "normie" use. Instead of trying to write init scripts and use a sysvinit startup tool, you can create human readable unit files, run systemctl to control startup, and read service logs(including systemd errors for said service) using journalctl. You don't need to decipher bash script or look online for examples. There are valid concerns like systemd's violation of GNU's "keep is simple" principle, Pottering's control/influence, and its size.* My thoughts on systemd are kind of mixed, to be honest. In the before time, systemd wasn't as widely used and wasn't very stable. You were better off with distros that used more traditional init in my opinion. However, we now have excellent distros that use systemd by default, like Arch--and the distros that benefited from the simplicity of foregoing systemd (in my case more specifically Slackware and later Gentoo) are more or less obsolete in their own ways. However, I still have yet to spend any time learning the internals of systemd. And if something is wrong with a unit, for example, I might just be kind of fucked. Whereas back in the day, even a relatively frightening failure in bringing up a service or what have you could usually be fixed with a bit of shell scripting knowledge. But let's be honest: that's my fault, and every problem I've had since switching to a systemd-based distribution has been solved by configuration changes completely unrelated to systemd itself.
At least if you search for an issue, you will get at least one answer on stack exchange or a forum, though the Windows "community" likely has fewer trannies.* The Linux community has always and will always be the worst part of Linux.
These days I think I would agree with you pretty broadly. I only became a systemd "user" a few years back when moving to Arch, but I've legitimately never had an issue in that time which wasn't totally unrelated to the aspects of systemd I actually interact with. Not exactly a huge amount of experience, but a few years using a given piece of software without it causing problems is pretty damn good by my usability standards. But in fairness, systemd does a lot and the extent of my interaction with systemd is limited. I only need to worry about basic functions: managing services, setting some config options, mounting a few remote shares on boot, and I also use systemd-boot.I personally think systemd is a better init system for enterprise and "normie" use. Instead of trying to write init scripts and use a sysvinit startup tool, you can create human readable unit files, run systemctl to control startup, and read service logs(including systemd errors for said service) using journalctl. You don't need to decipher bash script or look online for examples. There are valid concerns like systemd's violation of GNU's "keep is simple" principle, Pottering's control/influence, and its size.
It has gotten to the point where I think most of the drama in the linux community is from people who barely use or know linux as described in the video below. Linux software projects and distros are like sports teams to them.
At least if you search for an issue, you will get at least one answer on stack exchange or a forum, though the Windows "community" likely has fewer trannies.
Vidya runs fine on Linux. Valve has done a ton of legwork with Proton. And older games (pre 2010) run fine with Lutris and Wine.linux is good but i like my vidya gaems so i have to run windows anyway, and im too lazy to bother setting up and managing more than one OS on my machine
Some of them have small quirks and new/lazy linux users expect it to work flawlessly.
Vidya runs fine on Linux. Valve has done a ton of legwork with Proton. And older games (pre 2010) run fine with Lutris and Wine.
For the most part, yeah. But some DRM and anti-cheat just doesn't play well with Linux at all, mainly those draconian kernel-level bullshit that cumsoomers are happy to have on their system. For folks that enjoy indie or older titles that have had their draconian DRM removed, you're not really going to be affected. But for people who want to play a game that is AAA and has come out in the past year/two, you're SOL if it uses BattlEye, EAC, or Denuvo. Nvidia drivers are still weird as hell when it comes to Linux, too. Some people (like me) have no/minimal problems and can get things like Hashcat working right out of the box. Though, now I'm in the ballpark of "Hashcat doesn't work for me" ever since I upgraded from a 10 series card to a 30 series card. Other people get super unstable installs that just don't work right, even with a blood sacrifice. I wouldn't say Linux is a bad experience for gaming. It does have benefits, but you are probably going to have to put in research to get things working and some stuff just will never work.Vidya runs fine on Linux. Valve has done a ton of legwork with Proton. And older games (pre 2010) run fine with Lutris and Wine.