Oh, kanata looks great! Good to know!

In the earlier days of Wayland I was not able to reproduce the custom keyboard mappings that I set up with xkb. Xkb worked, but only in windows running under Xwayland. I know the common xkb presets, like changing caps lock to a control key, are reproduced in Wayland implementations. I had really custom mappings that required more general remapping capability.

I fixed my setup by building a keyboard with a microcontroller that I can program with ZMK. It’s a better setup, although it did take more time, effort, and money. The bottom line is I’m enthusiastic about Wayland, even though I had to find another way to reproduce one of my favorite features.

I got my kids started on Scratch - I recommend it! Syntax is communicated with puzzle block shapes. Statements have a tab on the bottom, and a matching slot on top; number and string values are pill-shaped; boolean expressions are diamond-shaped. If the pieces fit together, it’s a valid program.

As a NixOS user, any drama that might be going on doesn’t affect my use of the software

I use a chat interface as a research tool when there’s something I don’t know how to do, like write a relationship with custom conditions using sqlalchemy, or I want to clarify my understanding on something. first I do a Kagi search. If I don’t find what I’m looking for on Stack Overflow or library docs in a few minutes then I turn to the AI.

I don’t use autocompletion - I stick with LSP completions.

I do consider environmental damage. There are a few things I do to try to reduce damage:

1. Search first
2. Search my chat history for a question I’ve already asked instead of asking it again.
3. Start a new chat thread for each question that doesn’t follow a question I’ve already asked.

On the third point, my understanding is that when you write a message in an LLM chat all previous messages in the thread are processed by the LLM again so it has context to respond to the new message. (It’s possible some providers are caching that context instead of replaying chat history, but I’m not counting on that.) My thinking is that by starting new threads I’m saving resources that would have been used replaying a long chat history.

I use Claude 4.5.

I ask general questions about how to do things. It’s most helpful with languages and libraries I don’t have a lot of experience with. I usually either check docs to verify what the LLM tells me, or verify by testing. Sometimes I ask for narrowly scoped code reviews, like “does this refactored function behave equivalently to the original” or “how could I rewrite this snippet to do this other thing” (with the relevant functions and types pasted into the chat).

My company also uses Code Rabbit AI for code reviews. It doesn’t replace human reviewers, and my employer doesn’t expect it to. But it is quite helpful, especially with languages and libraries that I don’t have a lot of experience with. But it probably consumes a lot more tokens than my chat thread research does.

The problem with appealing to episode details is that the transporter is presented very differently in different episodes depending on the needs of the story. That’s fine for storytelling, but it means we can’t pin down a fixed set of rules for how transporters work. To ponder philosophical questions we have to invent rules by picking and choosing presentations of the transporter that seem most interesting, and filling in gaps with our imaginations.

Yes, there’s the episode where Barclay is conscious during transport. But there are contradictory presentations where Scotty puts himself in stasis in the ship that crashed on the Dyson’s sphere, and M’Benga putting his daughter in stasis. In those cases neither has memories of time during transport.

There is the episode where Picard uses the transporter to convert himself into an energy being to try to live in a space cloud. The story is the transporter converts matter to energy, and energy in Star Trek is another possible state of living existence. Thus continuity. But there is a contradictory episode of DS9 where crew members’ physical and neural patterns have to be stored in computer memory, not “pure energy”, and we see holosuite character versions of them.

So there’s either no suicide booth problem, or there is. You get to pick depending on which scenario you feel like talking about.

My favorite take on this question comes from Existential Comics

I haven’t used Forgejo, but from the docs it looks like it’s actions system is nearly identical to Github’s. And yes, that sounds like a good case for a scheduled workflow

Dammit - now I’m cringing at the thought of datomaceous earth in the USB port!

Yes, alongside state parks, which are funded at the state level.

Well you’ve got one visitor currently cranking it lol

I’ve done that too, and it’s not the same IMO. Ansible doesn’t put entries in the boot loader for older system states you can boot into in case you break something. It’s possible that Ansible configurations aren’t idempotent. The exact versions of packages that get installed can’t easily be managed with Ansible if you’re also regularly updating packages. There’s lots of stuff that is much easier to configure with NixOS and Home Manager. I found my Ansible configs were always out of date, which doesn’t happen with NixOS where editing the config file is how you make any system changes.

I think there are arguments for NixOS for a casual user despite the learning curve reputation. But there are also downsides to consider.

The pros:

• There is a good, user-friendly installer that makes it easy to get a working system
• From what I can see setting up KDE is pretty easy - there are configs online that you can paste into configuration.nix without modification
• NixOS is good for gaming with proprietary drivers and Steam - again it’s a matter of pasting a few lines of configuration
• Like with other distros it’s easy to recover if something breaks
• Unlike with other immutable distros you get a lot of options for tinkering with your system, and experimenting. You can dip your toes into the advanced stuff, going from casual user to Linux expert at your own pace, with the safety line of being able to roll back changes at any time.
• If you stick to the basics you can have a very stable, very update-to-date system without much difficulty.

The cons:

• To get the full safety of rolling back a previous point in time you need to ditch channels, and instead use pinned nixpkgs revisions. The best way to do that is probably using flakes - but whatever strategy you use you need to depart from the setup the installer gives you, and learn enough to remake your configuration.
• You’ll find contradictory instructions depending whether they’re written for use of channels or flakes.
• Going beyond the basics of installing packages, and using premade NixOS modules gets you into the infamous learning curve. For example I’m guessing that managing kwin scripts declaratively in Nix config might be an adventure. But managing them by hand the way you do in Fedora might be the same. (I haven’t tried this, so I’m not sure.)
• There is some stuff you have to know, like if you want to run binaries that weren’t built for Nix you want to set up nix-ld first.
• If you’re building software you have to learn to do things the Nix way because of the lack of FHS. That’s great for Nix fans like me, but frustrating for some.
• There is no graphical software center, nor automatic updates. You have to use the workflow of installing stuff by editing your config file, and get used to using search.nixos.org to find stuff. This is a pro from the perspective of having a stable system that can be rolled back to earlier states, but might feel less user friendly than a GUI workflow.

Even if you set up flatpak (which is easy to set up tbf) you’re probably going to be managing flatpaks using the CLI.

It would be easier for me to recommend NixOS if the installer set up a flake configuration with more niceties pre-installed, like nix-ld. The next best thing would be a de facto standard flake starter configuration for people to copy. But like I said, I think there is a case.

Since timely updates are an issue, specifically Debian Testing is a good stable distro.

I came here to make the same comment lol. My dog does look pretty unhappy when there is string in the butt.

The First Lady of Ferenginar?

• It has a nice interface for searching history - nicer than the history search included with the shells I’ve used
• It has a “workspace” mode - it remembers which directory commands were run in, which gives you the option to limit history search to commands run in the same directory, which are often most relevant to the project you’re working on in that directory
• If you want you can back up, or sync history to multiple machines. I know I’ve been in situations where I know the command I want is in history, but it’s in history on my desktop, and I’m on my laptop at the moment

He’s flying a future time machine, and it was made into a time machine before he started flying it according to objective time.

Yes, NixOS - and also Niri so your tiled windows don’t resize themselves, and you get the extra-fancy screen cast and screen shot features. That’s what I use, therefore it is the best.

I work with a very competent dev who uses Windows. I’ve even gotten him to the point of helping me to champion Nix dev shells. But he prefers to use those through WSL ¯\(ツ)/¯