I thought, the +? was going to be a syntax error. 🙃

Ah, interesting. In my current setup, I dump the auxilliary files into a folder above the repo, but it can certainly make it a bit messy to find the repo in there then…

I’d say, I’m primarily a very low volume gamer, so I don’t play a lot of games, and if I do, I don’t play them for long. And that certainly makes it easy to look at the news of a game releasing and to think, yeah, that’s probably neat, but if I’m buying another game then it’d be Undertale or Baba Is You or such, and it definitely doesn’t look as neat as those…

Huh, I practically only know Intel as having defects and vulnerabilities, but I didn’t know this had such a long history…

You could use this crate to build a Rust program which uses the Qt GUI framework and therefore would feel rather ‘native’ in KDE.
But the vast majority of KDE applications continue to be implemented in C++.

For a project called “Potato Peeler”, I’ll put it into a structure like this:

~/Projects/Tools/Potato-Peeler/potato-peeler/

Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.

Then the capitalized Potato-Peeler/ folder, that’s for me to drop in all kinds of project-related files, which I don’t want to check into the repo.

And the lower-case potato-peeler/ folder is the repo then. Seeing other people’s structures, maybe I’ll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.

I also have a folder like ~/Projects/Tools/zzz/ where I’ll move dormant projects. The “zzz” sorts nicely to the bottom of the list.

Is “code”, “designs” and “wiki” here just some example files in the repo or are those sub-folders, and you only have the repo underneath code?

I find that difficult. Aside from code reviews, often times your job as a maintainer is:

• getting a refactor or code cleanup in while everyone’s asleep
• shuffling commits around between branches
• fixing the CI toolchain
• rolling back or repairing a broken change
• unfucking the repo
• fixing a security vulnerability

A required review slows all of these tasks to a crawl. I do agree that the kernel is important enough that it might be worth the trade-off.
But at the same, I do not feel like I could do my (non-kernel) maintainer job without direct commit access…

Thanks. 🙂

A web search tells me the θ (lower-case theta) is used to represent an angle. Do you just fill in 0° – 359.9° one after another to draw that curve?

I used to have this kid as a colleague (he was 17 at the time), who had been primed by his parents to be a nationalist.

One of the times, he was completely bewildered by my stance was when I said that even if I cared about having things in common with other humans, I feel like I have more in common with the folks just across the border than those who live several hundred kilometers away within the same border.

You could really see the cogs in his brain churning, trying to grok how you can have things in common with team B, when you’ve been assigned to team A.

83°F = 28.3°C

I use a similar feature on KDE (along with a KWin script for tiling) basically just to set the background color of my translucent panel, so I can quickly tell workspaces apart. 🙃

Louis Rossmann. He’s only one employee of FUTO, so I’m not saying he’s personally responsible for or even particularly agrees with that page (although I wouldn’t know, if he is), but his public support for FUTO pushes those fanboys in that direction either way.

It annoys me so much, because it works.

There’s more people who have a vague understanding that “open-source” is good than people who understand software licenses, and nevermind people who actually go to compile the supposedly-open-source software to see what’s included.

And if multiple people tell you that LLaMA is open-source, at some point you’re just gonna assume that’s true rather than check the license/code yourself.

Hell, there’s even absolute dickholes which post their own definition of “open-source” like they’re the fucking OSI themselves: https://futo.org/open-source-definition/
But because a popular YouTuber is behind that scam, you now have fanboys putting into question whether the definition from the OSI, which literally coined the term by publishing the definition, is actually the correct one. Absolutely incredible.

Edit: While researching for the comment below, I found this page on the FUTO website, which says their open-source definition was just a very funny parody: https://futo.org/about/futo-statement-on-opensource/
Why they don’t take that open-source definition offline then, or preface it with a disclaimer, I do not know. And I think their reasoning for the parody is shit, but make up your own mind.

A distro is a complete installable operating system (+ a set of software repositories from which you can install updates and new software).
Many distributions (or their flavors/spins) will come with a default desktop environment and then usually also apply some distro-appropriate theming to that desktop environment.
If you look at screenshots of distributions, you’re likely just looking at screenshots of their themed default desktop environment.

And a desktop environment is essentially the GUI of your OS.
It includes software such as the panel/taskbar, the application menu, the systray, the audio system, icons, a login screen etc… It also typically comes with a set of default applications, such as a file manager, a terminal emulator, a text editor etc…
In a sense, the desktop environment contains essentially everything that differentiates a desktop OS from a server OS (the latter is usually just a terminal, without graphical interface).

Yeah, when I then used Visual Block mode to do the multi-line cursor, I realized I probably could’ve selected+yanked it that way, too.

But that is some good info nonetheless. I wasn’t actually aware of the different Visual modes…

Well, I’m at least not surprised. They didn’t achieve good face animations through technological advancement, but rather by throwing tons of money at the problem, i.e. hiring actors and motion-capturing them.

When it stops being your unique selling point, you’re not gonna get as much budget anymore, at which point it’s either scrapped or you might use worse equipment, worse actors and give the actors less time to practice and redo scenes.

In general, the problem with realistic graphics is that reality is your upper bound. It’s difficult to inch closer to it and it’s easy to regress when you don’t pay as much attention to some detail…

That is a very good question. It all started as a dainty test setup, and I guess, we had lost the routine of always scripting hardware setups, because our previous project hadn’t required it.

Obviously, the second-best time to start doing it is now, but I’d need to properly learn one of these first to be able to lead the way on that.
Which collides with me not really wanting to use any of the ones I’ve experienced so far (Ansible, Puppet) in my freetime. 🫠

Doesn’t that just cut one line at a time? Or is this Emacs-like, where it buffers the lines?

That host doesn’t have internet access, though, so installing a different editor wasn’t really an option to begin with…