Meow
imikoy
joined 2 years ago
I don't know how it is called in english, we call it vermicelli and it's a thin spaghetti with very short (around 2 cm) length.
It's very fast to make and doesn't require much camping around the stove.
Here's a frontier I want you to experience: 25g. and lower Kailh Choc switches.
They will probably require a different PCB because of different footprint (position of legs and contacts), but lightweight Chocs are sooooo satisfying, the actuation force is so small that resting a finger on a key can press it and it's GLORIOUS
Also, try split keyboards! My hands rest on the table, I don't need to move them, I just adjust the keyboard halves. And I can put a bowl of soup, a laptop, or a fully sized cat in between them! 
I don't care if the worm has nipples or not, I still love it.
I don't see dessalines under admin section on the .world homepage. Perhaps you are mistaking it for .ml?
Impressive
Split keyboard with very light (~25 g. force) Choc switches. Sofle, Helix, Corne, etc. Light switches make typing a pleasure, and you can put anything between the halves and position them however you like.
Popular keyboards will probably have case designs already made, if you don't want to have two somewhat bare PCBs on the desk. Though there's an upside to caseless keyboards - the hands can lay down on the table because the keeb is 15mm high.
"An entire OS" - that is NixOS. Nix (package manager / build system) can and is often used standalone, on other Linux distributions, and by some on MacOS.
I cannot vouch for ease of use of Nixpkgs' Go building facilities, but at the very least it should be possible to create a necessary environment for development and compilation of a package. Nix guarantees that it is going to be reproducible.
The main downside of using Nix would be that the declarative approach is different from the imperative one - AFAIK, there is no command to just add something to the environment (nix-shell -p does not count as it is a temporary env without a pinned Nixpkgs, so isn't reproducible). The second would be that Nixpkgs seems to only have one version of Go and Co. at a time, so if one needs an older version of something they need to find an older version of Nixpkgs.
edit: as I have looked up, there are actually four versions of Go - "go" is 1.20, and "go_1_*" gives 1.21, 1.19 and 1.18 (on unstable Nixpkgs). I don't know about other pieces of the environment though.
Valve does make substantial changes when they are needed - latest example is the switch to mesh-based maps instead of BSP trees in Source 2.
Official NixOS LiveCD has calamares, so that part is already figured out.
I think distributing a pre-configured system can be beneficial for people who don't want a bare system while they are still learning, but then there's the question of people already having different configs, if we are talking about people coming from other distros.
As I saw (and written), NixOS users tend to design a config in a way that it can be extended with new machines easily and with little code in flake.nix (even if this is utterly useless, like for me, since the devices in use don't change) and installed on a new machine, ZaneyOS demonstrates this well. I quess if a person wants to try Nix out they can install someone else's NixOS and then change it for themselves?
I think the distributed configuration will need a guide on how to change it before installation (where the dotfiles go, hardware side and partitions).
What about making a home manager config? Much less commitment needed than installing a whole new OS. And HM provides options geared for user's environment, so the user can change what matters to them the most at the current moment (while they are learning) - what they interact with.
P.S: since you are trying Nix out, state data control might interest you, since you can boil the system down to its configuration and a directory with all of the worthy-of-saving state. Also, home manager, of course.