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).

taping UE5’s graphics engine to GameBryo/Creation

I can imaging maybe writing an interface layer, but given the scale I kinda doubt they’d choose to do this.

IDK I could be wrong, but if we know they used UE5 my bet is the game was rewritten in mostly new C# and blueprint.