Yeah, I also recommend this. Particularly with laptops, it’s good to have a full-fledged desktop environment, since you’re more likely to need WiFi, power management, easy display configuration etc…

In case you happen to be on KDE, plasma-apply-colorscheme gets you pretty close, especially if you’re mostly using KDE programs.

I’m towards the hyperphantasic side of the spectrum and I’ve also noticed that it influences quite a lot of things.
Perhaps the biggest factor is that I don’t have the same drive to visit places or people. I could travel to a castle to look at it, or I could do so in my mind. I could meet back up with an old friend, but as I think of them, my desire to see them again is satiated. This does mean I’m terrible at maintaining friendships and socializing in general.

However there are things when the Ai is helpful, especially for writing tests in a restrictive language such as Rust.

For generating the boilerplate surrounding it, sure.
But the contents of the tests are your specification. They’re the one part of the code, where you should be thinking what needs to happen and they should be readable.

A colleague at work generated unit tests and it’s the stupidest code I’ve seen in a long while, with all imports repeated in each test case, as well as tons of random assertions also repeated in each test case, like some shotgun-approach to regression testing.
It makes it impossible to know which parts of the asserted behaviour are actually intended and which parts just got caught in the crossfire.

Yes, catastrophic software bugs…

Then you open it up and the single bean fills out the entire can. They had used a very big bowl for that photo.

That is a good tip. Unfortunately, I am too fish to understand it. 🙃

I just type ps and in 9 out of 10 cases, my shell suggests ps -ef | grep <process-name>. So, it’s actually less for me to type than “pgrep”…

Ah, that was a brainfart. I do use pkill primarily. I just use the other command, when I’m not sure what the process is called…

Yeah, I especially don’t understand it here, because it’s a graphical tool. You don’t have to keep backwards compatibility.

Even if you’re worried about people depending on the format that’s being piped, you could keep only the piped format stable. We have the technology.

Yeah, I would often just grab htop because I had no idea how to read the CPU usage out of top.
For example, for me it says:

%Cpu(s):  0,4 us,  0,4 sy,  0,0 ni, 98,8 id,  0,0 wa,  0,3 hi,  0,0 si,  0,0 st

Now that I look at it, I can guess that us and sy are supposed to be user and system time. And I guess id is supposed to be idle.
I have no guess what the other numbers might be, though. And well, I would often like to see the CPU usage per core.
Now I know that I can just press 1t and get effectively the same view as in htop.

I might learn top’s filtering workflow, too. But so far, I always killed processes with ps -ef | grep <process-name> and then kill <pid>, which isn’t particularly more cumbersome, so will see…

Damn, even when I don’t mention it, it’s apparently obvious that I’m gushing about Rust. 😅

I had the Rust CLI Book in mind: https://rust-cli.github.io/book/index.html
Especially, if you have experience in another language already, the first chapter shows you how to develop and ship a useful Rust application in a short amount of time. And then the second chapter contains all the detail information, which you might need, after you’ve run off and started building your own thing.

But yes, Rust By Example is also really great. It happens a lot that you search “xyz in Rust” and it’s one of the first results, and always worth clicking on.

I see the value in reading documentation front-to-back for picking up all the little tidbits of information (or at least knowing where they’re documented), but yeah, ultimately I need to be building something to really process the information.

Kind of my sweetspot is documentation that makes you build along, but doesn’t overstay its welcome. As in, don’t cram all the details along the way, but rather just dish out important information on rapidfire.
I will run off building my own thing in the middle of the tutorial, if that isn’t the case, whether I want to or not. As soon as it’s quicker to learn by dicking around with the code, I will do that and then I’ve spoiled future chapters, so likely won’t return.

What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected?

I know that the terminal emulator built into the JetBrains IDEs works that way…

Not sure about video playback, but I feel like the PeerTube website is much more efficient. The YouTube website is amazingly badly coded…

You generally have to fork to create a PR…

If we leave realism aside for a moment, though, the difference is that:

• a carry slot limit restricts how many distinct kinds of items you can have, whereas
• a carry weight limit moreso forces you to leave behind duplicates of items or to e.g. make a choice between heavy armor vs. having auxiliary items.

It depends on the game what’s more fitting for the overall design, but yeah, ultimately you want to prevent the player from optimizing the fun out of the game.
Having very heavy armor or dozens of healing potions can be boring, since there’s no risk anymore. But having one of each different kind of item can also kill the fun, because having the perfect solution for every situation is just as boring.

Yeah, and you’d often get a separate junk inventory, along with a one-click button to sell everything from there. I guess, at least it was an attempt to solve the problem…

I’d argue that rather than carry weight, the real culprit is shops where you can sell stuff. If you knew right away that junk is not worth picking up, because you can’t sell it, then you wouldn’t pick it up. And then the carry weight limit can do what it was designed for, which is to make you strategize what equipment to bring along.

I can’t really sell this as a solution, as it requires quite a lot more involvement than a simple configuration file should, but I use Nix Home Manager with Plasma Manager for this.

This is part of the tooling you’d use on NixOS, but you can use it on other distros, too, and it generally works fine (although I’m not sure, if the current version of Plasma Manager still supports Plasma 5, in case you’re still on a distro with that).

Basically, it allows you to define e.g. keyboard shortcuts like this:

    shortcuts = {
      ksmserver = {
        "Lock Session" = [
          "Screensaver"
          "Meta+Ctrl+Alt+L"
        ];
      };

      kwin = {
        "Expose" = "Meta+,";
        "Switch Window Down" = "Meta+J";
        "Switch Window Left" = "Meta+H";
        "Switch Window Right" = "Meta+L";
        "Switch Window Up" = "Meta+K";
      };
    };

It then fucks up the formatting, so that it looks like KDE expects, and throws it into ~/.config/kglobalshortcutsrc.
(KDE does actually have a text-based config, it’s just borderline unusable.)

Well, and you can do this with lots of other Plasma options, too. Here’s their official example: https://github.com/nix-community/plasma-manager/blob/trunk/examples/home.nix