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!