Conversation

Notices

1. James Smith 💾 (floppy@mastodon.me.uk)'s status on Tuesday, 06-Aug-2024 14:35:14 UTC James Smith 💾

   Slic3r was forked to PrusaSlicer which was forked to SuperSlicer and Bambu Studio which was forked to OrcaSlicer which includes a bunch of SuperSlicer as well.

   All of them except Slic3r are still active and have a diverging set of features. This does my head in.

   #3DPrinting

   • Dave M7TLB 🐞🇺🇦🌻 (thelovebug@mastodon.me.uk)'s status on Tuesday, 06-Aug-2024 14:35:05 UTC Dave M7TLB 🐞🇺🇦🌻

     in reply to

     @Floppy Standing on the shoulders of giants.

     I understand why Slic3r was forked, but why downstream didn't contribute to PrusaSlicer, I don't know.

     Although Bambu is a competitor to Prusa, so perhaps that's why?

   • Dave M7TLB 🐞🇺🇦🌻 (thelovebug@mastodon.me.uk)'s status on Tuesday, 06-Aug-2024 18:03:51 UTC Dave M7TLB 🐞🇺🇦🌻

     in reply to

     • ZeroZX

     @zerozx
     This is analogous to Gecko Vs Blink. Only Firefox uses Gecko (Cura), but most other browsers use Blink (Slic3r derivatives). All Blink-based browsers have their own discrete features, and Firefox will never adopt Blink 😁

     Bottom line is that the maintainers of each of these pieces of software believe they have the best version/variant... I think you'd struggle to get them to align.

     Please, I beg you, prove me wrong!

     @Floppy

   • ZeroZX (zerozx@social.tchncs.de)'s status on Tuesday, 06-Aug-2024 18:03:52 UTC ZeroZX

     in reply to

     • Dave M7TLB 🐞🇺🇦🌻

     @thelovebug @Floppy It would be great if all non printer-specific features would be upstreamed. If slicers came up with a common API for writing slicing plugins, maybe even Cura could benefit from some of these features (even though it doesn't not share the same Slic3r base)