In my past year(ish) of #3dPrinting, I’ve gone from Marlin, a c firmware to #Klipper, a (mostly) Python firmware, and from Cura, a (mostly) Python slicer to OrcaSlicer, a c++ slicer.
-
In my past year(ish) of #3dPrinting, I’ve gone from Marlin, a c firmware to #Klipper, a (mostly) Python firmware, and from Cura, a (mostly) Python slicer to OrcaSlicer, a c++ slicer.
I can’t really argue with the results of Klipper (jury is still out for Orca), but this seems backwards, especially considering the relative power of the compute these are running on.
-
@linux_mclinuxface Does Klipper use Python for the realtime OS parts as well?
-
@voxpelli no, that is C, but it is super minimal compared to Marlin.
-
@linux_mclinuxface the configurability of Klipper is crazy. There’s built in configs for just about everything.
-
@raykrueger you're not wrong, although a lot of stuff is configurable in Marlin as well to be fair, it's just not very ergonomic to make changes.
Tinkering with defines and Cross-compiling microcontroller code and fiddling with bootloaders is kind of a drag.
