PM_ME_VINTAGE_30S [he/him]

It can use ChatGPT I believe, or you could use a local GPT or several other LLM architectures.

GPTs are trained by “trying to fill in the next word”, or more simply could be described as a “spicy autocomplete”, whereas BERTs try to “fill in the blanks”. So it might be worth looking into other LLM architectures if you’re not in the market for an autocomplete.

Personally, I’m going to look into this. Also it would furnish a good excuse to learn about Docker and how SearXNG works.

LLMs are not necessarily evil. This project seems to be free and open source, and it allows you to run everything locally. Obviously this doesn’t solve everything (e.g., the environmental impact of training, systemic bias learned from datasets, usually the weights themselves are derived from questionably collected datasets), but it seems like it’s worth keeping an eye on.

Google using ai, everyone hates it

Because Google has a long history of doing the worst shit imaginable with technology immediately. Google (and other corporations) must be viewed with extra suspicion compared to any other group or individual because they are known to be the worst and most likely people to abuse technology.

Literally if Google does literally anything, it sucks by default and it’s going to take a lot more proof to convince me otherwise for a given Google product. Same goes for Meta, Apple, and any other corporations.

If Justin/anyone at Cockos is reading this: please open-source REAPER. You really would be doing the audio community a huge service.

Theoretically this exists: https://github.com/Nikilites/nuzu

Also, I managed to install the Flatpak of Yuzu off FlatHub about a half hour ago.

What are you doing in assembly?

I want to help but I’m making zero money. Zero times any percentage is zero.

Yeah when I searched for “insert-mode” from another comment, the next suggested result was “insert-mode vim” and “insert-mode visual studio” (which IIRC is just aping vim), plus it’s /c/programmerhumor so I had a feeling that it would be vim shenanigans.

Wait doesn’t Shift + I just type “I”?

Home is God-tier, just as useful as End when editing stuff.

I mean “ruined” is a bit strong, right? I’m no fan of Jimmy Wales but Wikipedia is still pretty good IMO for non-political stuff. It’s my first choice to look up math stuff so on that basis alone it gets my vote.

I’m on Debian because the software in the Debian repos is stable. So for mission-critical software, at least for my purposes, I’ll pick the version in the Debian repo, especially if it requires detailed integration with the operating system such as real-time audio. If the software does get updated, it is probably important and nearly guaranteed not to break. A great example has been KDE Plasma: I don’t get the bleeding-edge features, but it’s been a rock-solid, fast, still modern desktop environment on every computer I installed it on, including an old laptop that is so underpowered that Windows 10 is a Power-Point presentation upon a fresh restart. If Debian takes several months or longer to update it’s Plasma packages to Plasma 6 when it comes out next year, that would be fine for me because I don’t desperately need any new features from Plasma.

However, for software that really benefits from being up-to-date and isn’t a showstopper if it breaks, for example FreeTube, I prefer the Flatpak. I primarily use Discover for simple package management and upgrades, and it was trivial to install the Flatpak backend, so now my Flatpaks get updated like anything else. However, Librewolf (a browser, which I prefer to keep up-to-date) is installed from a non-Flatpak external repo because I had problems giving its Flatpak version webcam permissions (even if I enabled them in Flatseal).

AppImages have been great for working on new computers because I can (usually) just download them and go. Except for programs that I expect to be portable, I don’t typically use them in the long haul. Still, they’re super convenient to have around.

I don’t touch Snaps because of the closed-source backend and their role in Canonical’s transparent attempt to lock down Ubuntu, but if they open-source the backend I might consider trying them.

IMO part of why I’ve stuck with Linux is because there is (usually) a choice of how to compute. I.e., there are several ways to solve a problem where Windows or Mac would pigeonhole you into their workflow. Having multiple options is inherently a good thing as far as I’m concerned, even if I don’t use all of them.

See that’s what I thought, and that’s what I got from simulating both systems in the virtual machine, but on my particular hardware LXQT ran a tad bit faster. I tried a few straight-up WM’s but I didn’t like them. On my main PC, which is about five years old, LXQT ran about as fast as KDE and LXDE was predictably wicked fast.

I’m reinstalling Linux onto a legitimate hard drive (it was on a microSD). I’ll install both again and see what happens. Although really, I just need enough to run TeamViewer so I can control my other machines from there.

Tl;Dr: it’s not as hard as you think.

I just jumped over to Linux in June. I booted into the Debian Live USB with KDE Plasma as the desktop environment. In general, make sure you have an Ethernet connection available for the first install. I basically tried it out in the live environment for a few days and I fell in love with it, in particular KDE Plasma. I picked Debian because I prefer not to update my PC very often (or at all on my music production computer), plus I had a nice time with the Raspberry Pi, which uses a derivative of Debian. If I really need the absolute newest version of any specific software, I have no problem installing it from a .deb and I can usually compile from source if the project is decently documented, but if you absolutely do not want to do that, you might want to pick a different distro. Whatever distro you pick, you’ll be able to install KDE Plasma later. KDE had all the features I actually liked from Windows 10, but just better and more customizable. You can really make KDE work for almost any workflow.

I ended up installing it onto my music PC in a dual-boot configuration with my existing Windows 7 install. Unfortunately, I cannot afford to migrate my music production projects off Windows 7 because I was sloppy over the course of a decade with project directory structures and multiple drives, so I probably can’t move these projects to any OS until I put in a few weeks of work to actually organize all those files. Oh well; everything else can work with Linux.

I’ve gotten pretty far so far by just installing Wine and Proton and using my existing Windows programs through those compatibility layers.

I also dropped Debian onto my school/work laptop in a dual-boot configuration with Windows 10. Except for the background, which I decided to make different, KDE is almost indistinguishable from Windows 10 until I start to use it, which reminds me how much nicer KDE is to use.

Most distros have live USBs with easy installers that make the whole process really painless. I basically installed Debian in the background while watching TV (Invidious), all inside the live install.

I also put Debian with LXQT on the remains of my old highschool PC, basically just a motherboard with integrated graphics, RAM, CPU, and case; no hard drive, no external graphics. I just put Debian onto a microSD card [1] and told the BIOS to look there for bootable drives. No commitment. As much as I love KDE, it does require non-trivial resources to exist. Since that hardware is over a decade old now, I really can’t afford to give any of it to a desktop environment.

So if you really can’t commit to Linux, you can slap it onto a large microSD and tell your BIOS/UEFI to boot it. It’s a little slower than putting on a drive, but sufficient to give Linux an extended test-drive.

You could also try installing it in a virtual machine. Linux plays very nicely with Virtualbox. I picked LXQT for my old PC by installing a virtual machine with Debian and installing a bunch of desktop environments onto the system. Then, I cut back the number of cores, processor speed, and RAM available to see how they acted.

My point is, I really think it’s a good idea to try Linux now. It really will not take very long to get a great, usablr system, and you can make it yours by making little changes as you go along.

[1] Meaning, I used a live install USB to install to a separate microSD card. A live install loads the entire OS and any programs you install into RAM. In general, the content of the live USB isn’t changed, and it’s difficult to do so. What I did was to treat the microSD card as a hard drive and install a normal system.