62 lines
8.5 KiB
PHP
62 lines
8.5 KiB
PHP
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<?php include '../php/header.php';?>
|
|
<meta charset="UTF-8">
|
|
<meta name="description" content="List of things I hate.">
|
|
<meta name="author" content="speedie">
|
|
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
|
|
<title>Sucks</title>
|
|
</head>
|
|
<body>
|
|
<div class="content">
|
|
<h2>Sucks</h2>
|
|
<p>This page is a list of software, and just general things that absolutely suck. This page was inspired by <a href="https://suckless.org/sucks">the suckless page</a> under the same name and cat-v's list of harmful software.</p>
|
|
<h3>Technology</h3>
|
|
<ul>
|
|
<li>The modern web and web engines</li>
|
|
<p>The modern web is terrible and bloated. The bloated web leads to bloated browsers, which leads to severe security vulnerabilities and insane hardware requirements. Seriously, there is more complexity in designing a modern web browser engine than designing a desktop operating system. That's insane. <a href="philosophy.php">More information regarding the state of the modern web</a>. Several replacements for the web exist, but they have all failed to gain a userbase as normies demand the "fancy" and bloated mess we have today.</p>
|
|
<li>Wayland</li>
|
|
<p>Wayland aims to be a less bloated protocol, and while it does do some things better than X11, most of the bloat comes from the X.org implementation of the X11 protocol. While Wayland claims to be less bloated, much of Wayland's bloat is passed on to the compositor, which has to implement all of that. Writing a Wayland compositor from scratch takes a lot of effort, requires implementing a lot of different protocols, compositing, window management and more. A Wayland compositor is pretty much a full Wayland implementation, and more on top of that. For this reason libraries like wlroots exist which write a lot of the boilerplate for you.</p>
|
|
<p>Wayland also combines the window manager and compositor, meaning you cannot write a window manager without writing a compositor and vice versa. If a compositor manages windows well, but sucks at compositing then you're SOL. While Wayland objectively provides better security than X11, Wayland clients are also not allowed to place themselves in a specific position of the screen in the name of security. So when you try to use <code>--x-position</code> and <code>--y-position</code> arguments in spmenu and find that they don't do anything, you know who to thank for that.</p>
|
|
<li>Smartphones</li>
|
|
<p>Smartphones have done an insane amount of damage to society over the past 15 years or so. While I cannot deny that smartphones have replaced a lot of single use devices for most people, such as cameras, they are portable tracking devices that always lets the cellphone provider and very likely the governments know your location at all times. This cannot be avoided even with free software. But of course, they all run nonfree software by default anyway, and cannot be upgraded. No real replacement exists, and society is slowly making these portable tracking devices mandatory.</p>
|
|
</ul>
|
|
<h3>Operating Systems</h3>
|
|
<ul>
|
|
<li>Microsoft Windows</li>
|
|
<p>Microsoft Windows is the definition of malware, and it's malware that most people use. In addition to ethical issues and Microsoft having unjust power over their users, Microsoft is STILL not able to design a consistent UI that doesn't suck. You don't need to try hard to find 20+ year old UI elements that shouldn't be kept. There are a few replacements, such as GNU/Linux, and BSD operating systems.</p>
|
|
<li>Linux Mint</li>
|
|
<p>Linux Mint is a good GNU/Linux distribution, but I was recently made aware of the fact that they <strong>recommend</strong> nonfree software such as Discord in their software repositories, so I am no longer going to recommend Linux Mint to people.</p>
|
|
<li>PopOS</li>
|
|
<p>PopOS, a GNU/Linux distribution using the GNOME desktop environment as of 2023 is recommending nonfree software too in the software repositories. Not just provide, recommend. As such, I will not be recommending PopOS either.</p>
|
|
<li>OpenSUSE</li>
|
|
<p>OpenSUSE is a GNU/Linux distribution who seems to think that <a href="https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/XJOJEIKHH5GCFRIMZVWXSXJSJW2HTQGK/">people who do not want to see LGBT colors when starting LibreOffice are rotten flesh and 'Cutting out the rotten flesh is healthy and needs to be done.'</a> This behavior is not acceptable, but is a practice starting to become more and more common in the technology space. Software should be free as in freedom, and you should be provided with the four freedoms regardless of what you believe in.</p></p>
|
|
<li>Red Hat Enterprise Linux (RHEL)</li>
|
|
<p>On June 21st 2023, Red Hat announced on the Red Hat blog that Red Hat Enterprise Linux (RHEL), a GNU/Linux distribution <a href="https://www.redhat.com/en/blog/furthering-evolution-centos-stream">is becoming nonfree software</a>.</p>
|
|
<li>BSD philosophy</li>
|
|
<p>The BSD operating system is good, but I believe the BSD philosophy sucks. While the core utilities are perfectly fine, BSD is not copyleft, and they are strongly against the practice of copyleft software and copyleft licenses such as the GNU General Public License. I will continue to use BSD but I hate their ideas and will GPL all my software when feasible.</p>
|
|
</ul>
|
|
<h3>Software</h3>
|
|
<ul>
|
|
<li>libvirt</li>
|
|
<p>QEMU is just too complex for most people, and as such someone decided that we needed to develop a XML configured frontend for QEMU called libvirt which is just <em>barely</em> easier to use but barely works and breaks core functionality constantly, notably PCIe passthrough with quite a lot of devices. There is no real replacement, other than just using QEMU by itself, which is possible.</p>
|
|
<li>Flatpak</li>
|
|
<p>Because we have so many terrible package managers, someone decided that it would be a better idea to introduce yet another terrible package manager, one that bundles all libraries the program depends on together into one container, wasting the user's storage space with 50 different copies of the same thing. The only valid use for Flatpaks would be server use or maybe a system with musl libc when a program only compiles with glibc. There are many replacements, such as the normal package manager you're already using (I hope).</p>
|
|
<li>AppImage</li>
|
|
<p>AppImage is what happens when a Windows developer comes to our operating system, refuses to admit package managers are superior, and instead decides to bring the Windows tradition of downloading executables from the internet and running them to our operating system. AppImage has (thankfully) slowly declined in userbase due to not updating fuse and popular distros dropping the older fuse version. Replacements exist, such as your normal package manager.</p>
|
|
</ul>
|
|
<h3>Toolkits</h3>
|
|
<ul>
|
|
<li>GTK</li>
|
|
<p>GTK used to be a good toolkit, but as the years progressed it went from being a customizable, hackable toolkit to a toolkit which only works well with GNOME. One might attempt to make a theme for GTK, but doing so is not at all trivial, and to apply said theme you NEED to use a graphical program. In theory QT would be a replacement, but it suffers from the same problem, only it's designed for KDE rather than GNOME. Most toolkits are just garbage.</p>
|
|
<li>QT</li>
|
|
<p>QT has the exact same problem, except it's for the KDE desktop rather than the GNOME desktop. At least QT looks like a Windows desktop by default though and not Mac.</p>
|
|
</ul>
|
|
</div>
|
|
</body>
|
|
<footer>
|
|
<?php include '../php/footer.php';?>
|
|
</footer>
|
|
</html>
|