For whatever it’s worth, I use (up until fairly recently) KDE Plasma on Arch, and it’s pretty much fine. There’s some hiccups especially after a big update such as KDE Plasma 6, but it’s a smooth ride so far.

If the KDE Plasma developers support an Arch-based distro of their own, and package stuff for this distro with care, I think it’d be a better experience, but I am guessing not by much compared to KDE Plasma on base Arch.

Not too sure if they outright lied, but I suppose we can say that they used the change to make their drives seem larger!

That’s why I wished computer people had used a prefix system distinct from the SI ones. If we’re measuring our storage devices in yeetibytes rather than gigabytes, for example, then I suppose there’s less chance that we’ve ended up in this situation.

I realized why I didn’t think of base 2 in my previous reply. For one, hexadecimal (base 16) often used in really low-level programming, as a shorthand for working in base 2 because base 2 is unwieldy. Octal (base 8) was also used, but not so much nowadays. Furthermore, even when working in base 2, they’re often grouped into four bits: a nibble. A nibble corresponds to one hexadecimal digit.

Now, I suppose that we’re just going to use powers of two, not base-2, so maybe it’d help if we do a comparison. Below is a table that compares some powers of two, the binary prefixes, and the system I described earlier:

Each row of the table (except for the rows for 2¹⁰ and 2⁵⁰) would be requiring a new prefix if we’re to be working with powers of 2 (four apart, and more if it’d be three apart instead). Meanwhile, using powers of 16 would require less prefixes, but would require larger numerals before changing over to the next prefix (a maximum of 16⁴ - 1 = 2¹⁶ - 1 = 65 535)

One thing that works to your argument’s favor is the fact that 1024 = 2¹⁰. But I think that’s what caused this entire MiB vs. MB confusion in the first place.

However, having said all that, I would have been happy with just using an entirely different set of prefixes, and kept the values based on 2¹⁰.

I guess? I just pulled that example out of my ass earlier, thinking well, hexadecimal is used heavily in computing, so maybe something with powers of 16 would do just fine.

At any rate, my point is that using a prefix system that is different and easily distinguishable from the metric SI prefixes would have been way better.

I think the biggest mistake there is using SI prefixes (such as kilo, mega, giga, tera) with bytes (or bits) to refer to the power of two near a power of ten in the first place. Had computer people had used other names for 1024 bytes and the like, this confusion between kibibytes and kilobytes could have been avoided. Computer people back then could have come up with a set of base·16 prefixes and used that for measuring data.

Maybe something like 65,536 bytes = 1,0000 (base 16) = 1 myri·byte; ‭4,294,967,296 bytes = 1,0000,0000 (base 16) = dyri·byte; and so on in groups of four hex digits instead of three decimal digits (16¹² = tryri·byte, 16¹⁶ = tesri·byte, etc). That’s just one system I pulled out of my ass (based on the myriad, and using Greek numbers to count groups of digits), and surely one can come up with a better system.

Anyways, while it’d take me a while to recognize one kilobyte as 1000 bytes and not as 1024 bytes, I think it’s better that ‘kilo’ always means 1000 times something in as many situations as possible.

Oh, this is supposed to be on a separate comment, so here it is.

Things used:

• Launchers: anyrun and rofi (rofi -show drun)
• File manager: thunar
• Terminal emulator: foot
• Bars and widgets: eww
• Notifications manager: swaync

If the earliest sports were a way to practice skills needed for hunting or warfare, then making an e-sport out of spreadsheets is going back to the roots of sports. It’s practicing skills needed for your daily job.

Using Arch with KDE Plasma too. My only problem with KDE‌ Plasma is that I just can’t stop customizing it. I find a couple of things that “I can do something to improve upon” and the next thing I know I’m tweaking things again!

Other than the odd problem with Wayland/XWayland or something, that I usually just make a mental note to investigate further, I’m pretty happy. Now if I‌ can only stop myself from “making just one more little change…”

I’ve used Librewolf until pretty recently and I say it’s not for everyone. It’s hardened Firefox made into its own thing for people who want the benefits of hardened Firefox but don’t want to go through the effort of hardening their Firefox install.

There are some sites that wouldn’t work in the strictest settings. As far as I remember, the most problematic sites with Librewolf are those that demand way too much in terms of privacy and security, so I took it as a given that if a site doesn’t work with Librewolf (with me using the default settings), it’s not worth it to enter to begin with.

Yeah, I’m sorry. I’m biased against it, thanks to my experience with it.

Well, I can take solace in the fact that 99.9% of the packages you are using are in EndeavourOS too. So, I was mostly right. :)

Yeah, also I think EndeavourOS and Arch moved to Plasma 6 at around the same time too? I tried holding off the update to Plasma 6 for a few days but finally took the update on March 12.

I also wish we could replace Manjaro with a green themed EndeavourOS. Manjaro is the next biggest Linux honeypot after OpenOffice.

I think with enough faffing around customizing things in KDE Plasma, I think a green-themed EndeavourOS is doable. Would I recommend it? Not really, lol! From what I’ve seen, I‌ like EndeavourOS’ default theming.

It’s just a shame EndeavourOS isn’t as known as Manjaro (at least during the time I first jumped into running Linux as a daily driver). But then again, with Manjaro shitting the bed becoming more known, I‌ hope EndeavorOS can take the place of Manjaro as the Arch-based distro for newbies.

Converting Manjaro to Arch in place is a labour of love. I have done it myself and it is was more steps than I expected it to be. Worth it though. Good friend.

Oh yeah, I was there with him when he was doing it. I can’t do any help other than cheering him on, and to have another eye on the screen making sure he doesn’t make any stupid mistakes in the process. At few points, I reminded him of the fact that I’ve backed up my files, and if things really get FUBAR, we can just do a clean install and restore the files from backup.

… I actually use Arch. Sorry.

But really, I would have gone with EndeavourOS (instead of Arch) if it were not for my friend who really strongly advocated for Arch (even installing it for me—or rather, converting my Manjaro install into an Arch one).

If I’ve had any regrets in my Linux journey, it’s choosing Manjaro instead of EndeavourOS as my introduction to Arch-based distros.

I’m with you on liking multi-monitor set-ups. I also have several workspaces and activities (a KDE thing—you can think of it as another set of workspaces accessible via a shortcut key), which means I’ve got tons of “space” to play around with.

I‌ could have my e-mail program run on one workspace, then switch to my main workspace with one screen for VSCode (or whatever) and another for the browser window with lots of tabs that I can just refer to while doing work. And then in a different activity, a multi-media program might be playing a podcast or just some music to help me focus.

My discord is usually on the same activity as my multi-media program though, as I don’t really need to refer to it as often. If there’s a new message for me, my system gives me a notification and an icon in my system tray lights up or something, indicating a new message.

But yeah! You do you with your preferred workflow!

Yeah, using Arch is a commitment. On top of having to keep your system relatively up-to-date (this is probably the easiest part though), you also have to be ready to do some work in resolving problems when they do crop up (usually after an update, lol).

However, I think most of the work in using Arch is the installation process, making sure things run smoothly after installation, and hammering out the kinks that may arise. After that, so long as you keep your system relatively up-to-date (and having resolved any issues resulting from updates), it’s mostly hassle-free.

The only other distro (or rather, OS) that I think has as wide a source for installable software is NixOS, but not only I haven’t any experience with it, it’s still relatively new and wouldn’t recommend it for daily-driving, much less gaming.

But yeah, Arch is definitely not for the faint nor half-hearted, but it might just work out for you. Good luck and may you be able to find a Linux distro that works with your hardware.

I can’t really give you advice but maybe my current set-up can give you some ideas.

My desktop has an AMD Ryzen 5 3500 for my CPU and an AMD‌ Radeon RX 7600 for the GPU and some 16GB of RAM. I have two cheap monitors both connected via HDMI and are 1080p 75Hz. My desktop runs Arch Linux with KDE Plasma 6 Wayland, and aside from some minor keyboard-related issues, it’s running fine. My desktop set-up could be just bog-standard that things just work, but there ya go.

I am not telling you to install Arch Linux, not unless you’re willing to dive into the Arch Wiki, lots of forum posts and the occasional Stack Overflow thread whenever you’ve got a problem—not to mention dive into the command line and read lots of arcane logs to even start to know what to search for online. However, if your problems are due to lack of software support or something similar, then with Arch (or really, Arch-based distros, just stay away from Manjaro) and its wide array of packages, you might just be able to make things work for your hardware.

I switched to Wayland the moment my distro went moved to KDE Plasma 6 because according to my logic: if things are going to be broken and I’m going to adjust to them anyways, I might as well do it all at once: shock therapy style.

Plasma 6 broke a lot of my desktop customization, but that is to be expected. And Wayland? It has been surprisingly okay. I am experiencing some keyboard-related problems that I can’t even begin to track down (sometimes the keyboard flat out refuses to work for certain programs, sometimes it’s the numpad). However, I am not sure if it’s really related to Wayland, so I’m withholding judgement.

This might be a stupid question, but I‌ wonder why they (datacenters) can’t recover the water they use especially if it’s in the order of magnitude that it significantly impacts water resources in their area.

I might be missing something big here, but I am imagining water-cooled systems that transfers heat to the water, but the water is otherwise unused. This water might not be able to be fed back (to the water sources in the area) as is, but it can be cleaned up and cooled down, and then be used for other purposes, right?

I actually have some plans (no timeline though, it’s basically just a wishlist item as of now) of making my own NAS, so there’s that opportunity. And of course, yeah, getting an old machine is also an option. Who knows, maybe I’d get my hands on another old laptop that could very well be my way to testing Linux distros.

That sounds amazing, to be honest. One major concern I’ve got is the initial setting up. That same friend of mine (the one who exorcised my system) already has a NixOS system for their NAS, and seeing the config files kinda scared me. However, as far as I’ve understood their explanation, it’s basically a “set-up once and forget about it” affair. It’s still quite a departure from the way I’ve learned to do things though, so it’s still intimidating.

To be honest, maybe I’m just waiting for that friend to be somewhat of an expert in NixOS, so that they can push me into using it, lol!

Initially, I chose Linux for it being gratis, but as I’ve used it more and more, I started to appreciate its freedom. It’s really kinda moot though since I first gotten exposed to Linux because I had to. Our uni adopted Linux (some faculties used Linux Mint, others used Ubuntu) for their school computer laboratories after they couldn’t pay for their Windows licenses. In a way, I indeed got into Linux because it is gratis.

I started daily-driving Linux when my Win7 desktop broke, and had to use an ancient, hand-me-down, laptop. It can barely run Win7, and so I tried installing Ubuntu on it (funny in hindsight though, I should have used a lightweight Linux distro). Then a friend of mine introduced me to Manjaro. It worked well for quite a while, until the HDD finally croaked (it’s had a long life of nearly a decade). I stuck with Manjaro when I got my present desktop, but that same friend of mine who introduced me to Manjaro pushed me to using Arch despite my protests. I would have wanted to switch to Endeavour instead since I was intimidated by pure Arch. But since they offered to do the “installation and set-up process” with me, I relented. (The scare quotes are there because it was not an ordinary installation process: my friend basically exorcised the Manjaro out of my system.)

I have a few distros I would like to try, off the top of my head: EndeavourOS, Fedora Silverblue, and NixOS. However, I don’t think I’m a distro hopper. I would prefer that I stay with a distro unless I get pushed off it for one reason or another. Perhaps, if I’ve got an extra computer to test things out, I might be a bit more adventurous and go distro-hopping using that extra machine.

To date, I’ve only had a bit of experience with Linux Mint and Ubuntu, and a bit more experience with Manjaro and Arch Linux. I don’t think fairly limited experience with those allows me to pick a favorite, but I suppose despite its reputation for being hard to use, I quite like Arch Linux. Its package manager as well its repositories really does it for me. It’s changed the way I think about installing programs, as well as updating them.

Currently, I use Arch and Win10 in a dual-boot system. After I’ve gotten myself an AMD graphics card, I spend my time on my Arch system almost exclusively.