160
Got this pamphlet for a 3d printer and they're boasting "proprietary software!" on the flyer like it's a pro and not a con
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Jul 2025
160 points (100.0% liked)
3DPrinting
19168 readers
68 users here now
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe/ may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is 
Moderation policy: Light, mostly invisible
founded 2 years ago
MODERATORS
Proprietary "can" mean better support. But that's asterisk heavy. Often that comes down to commercial hardware putting up road blocks to competitors. Or the open source solution being the product of a single developer in their spare time.
Proprietary often means "support, as long as we have to, then fuck you".
I learned the hard way, by selling proprietary products from a corpo that promised support. Would unironically be better off manufacturing them myself.
Oh absolutely. You're preaching to the choir here. Part of the reason I have a lot of hope around riscv. The processor designs themselves aren't necessarily open source. But with the ISA being open and open source the first to embrace. It "could" foster a new much less proprietary ecosystem.
Not really. The software being proprietary turns support into a monopoly.
The support can still be better, but it will be despite the software being proprietary, not because of it.
(And by the way, single developers on their spare time create proprietary software too.)
You aren't disagreeing with anything I said. It's all very asterisk-y. And if my personal preference/position is unclear. I run non proprietary *nix systems at a 7:1 ratio to proprietary. Precisely because of the better support. Come October that ratio is going to be getting even more lopsided.
It's not because the dev is on their own that others can't offer separate support.
One can acquire experience anyway offer to review the code of the solution upon noticing an error at a client that can't be fixed with some google-fu.