I don't care if my 3d printer is "open" any more than I care if my refrigerator is "open". I get that for a lot of you it's a hobby that you want a dedicate a lot of time to, upgrading, hacking, etc.. which is great. But for me, I just want something that prints when I need it to print. The fewer minutes per month that I have to spend thinking about or interacting with my 3d printer, while still getting great prints, the better. And that is what Bambu has nailed better than anyone else, as far as I'm aware.
Your fridge became dependent on updates. Then they added ads to front panel. Then they'll say that you need a subscription to use holiday mode. Then it no longer receives update and touch panel stops working because it can't connect to servers and you'll need to buy a new one or buy an upgraded touch panel for $99 instead of $199 if you'll buy it this week.
Well, I too, don't have anything against a company selling a "good but not open printer", and I don't care if my fridge is open.
However, I hope you see that the behavior reported by Jeff here is just bad. They are either not understanding open source licenses or are acting in bad faith.
The issue is not that they sell 3d printers with proprietary software. The issue is altering the deal _after_ you have purchased the printer. People bought a printer that was open. Then suddenly the company changed their mind and pushed an update that made it non open. And when people try to restore the software to the state it was when bought, the company fights such attempts with dmca requests. If I bought something it's mine and I can do whatever I want with it and run whatever software I want on it.
Yeah this practice needs to end. You buy a stack of hardware+software that does X.
Imagine if pizza consisted of software and hardware and you only bought hardware but software could be changed by dev/seller. Now your pizza shrunk in size, changed taste, or could only be eaten by a fork that is supplied for free by the pizzashop, otherwise special chemical compounds would make it disintegrate if you'd try to eat it using your hands or anything else. Technically you still have that pizza you bought...
Then you sound like the type of client that perfectly fits Bambu's profile. Now, don't come complaining when Bambu decides you need a monthly subscription to use the slicer, or whatever rent-seeking they come up with in the future. Remember, you are paying extra for the privilege of not thinking, and you bought into that arrangement fully aware.
The fact of the matter is that other people are likely annoyed by your slowness, and probably think lesser of you as a result, even if it's unjustified, and even if they're just doing it subconsciously. Sounds like you're aware of that and think it's worth the tradeoff. But you're probably not going to make much headway in destigmatising it. You're literally jumping in a bucket full of elderly people.
You literally linked to a website that overlays two unrelated graphs that look similar on top of each other. And now you're blaming others for coming to the obvious conclusion that you think "moving slower" and "growing older" should appear on that website.
Ignoring how many counter examples of this there are, why wouldn't Gaben do this given that he's majority owner of the company? He can do whatever he wants.
Bun is the largest project written in zig. And it isn't close. Bun is bigger than zig itself. Seems like zig isn't mature enough to handle Bun's needs, so I don't blame them at all for looking for off ramps. Only time will tell if rigidity from the zig team is worth the cost of losing Bun. It might be.
Zig won't be affected by Bun potentially moving to Rust, the language has been growing rapidly and one of the main proposals of Zig is "maintain it with Zig". It's ability to integrate with existing C code bases, as well as be a drop-in build replacement, has widespread use.
In addition, the link in the comment you replied to explains why the PRs Bun opened to Zig would have lowered the quality of the compiler and how Zig has achieved even greater speedups, with more widely applicable features like incremental compilation and the self-hosted backend.
reply