rklm

This was my first concern as well... Although I suppose you could do some test prints to collect values to change the simulation.

If I were printing something really big, I'd probably run a sim first even if it were inaccurate, just to see if there is an obvious problem.

I'm not sure this would help new people much though, since you'd have to be very familiar with your printer/printing to use a simulation anyway.

Looks pretty, and familiar to vscode. I'll check it out!

I used vim for all of my personal stuff until switching to vscode a few years ago, so an editor inspired by neovim is exciting!

Also,

No Electron. No VimScript. No JavaScript.

Hah! Shots fired, I love it

I had some coworkers a long time ago who swore by jetbrains, but I've never tried it. Maybe I should give it a shot!

I recommend using a kernel virtual machine.

KVM comes with the Linux kernel.

If you want to set it up manually, you'll have to look into qemu and virtio.

If you want a more virtualbox-like experience, you can use boxes (also called "gnome boxes"), which gives you a very simple UI for setting up VMs (including windows) with networking/shared drives/hardware pass through/etc.

Distrobox is just a set of shell scripts that controlls Podman under the hood. Not only is it like docker, it literally uses the same container format (ContainerD).

And they used the Naomi (arcade dreamcast) as the starting point for the main board

I think normally you'd loop it into the ejection port and out the magazine well, but that sort of lock is a poor security device for a firearm anyway

I think this is pretty close

This is a great write-up! I'm going to save it for reference.

Thank you!

I also use my steam deck as my daily driver (dockcase 10 in 1 with peripherals etc).

I had been using arch for years before I got the steam deck, and for the first 8 months or so I unlocked the btrfs partition and installed everything I needed normally (kvm/qemu, devel libraries and Linux headers for c++ development, etc)... But every update from valve would destroy my environment and I had to run custom scripts to fill my etc directory back in...

For the past many months I've been using distrobox (which I believe comes pre-installed on the latest steamdeck updates) with a rootless arch environment inside, and flatpaks for everything that requires systemd.

You can symlink things like xdg-open from inside the container to your host, and end up with a pretty seamlessly integrated experience (distrobox does a lot of this for you anyway, and comes with utilities which make this pretty easy.)

If you want direct control of the system, this is not going to be a convenient setup, but if you're interested in treating it like an immutable OS, there are userspace ways of getting around it's limitations.

SteamOS has inspired me to make future installs immutable (and atomic/declarative using containers?), because it can be kinda nice once you get used to it.

I hope this helps or was interesting!

Edit: This is specifically what I meant by symlinking xdg-open.

Idk if this is done by default now, but if link handling is broken this is how you fix it