I didn't know it was impossible to build businesses without inserting to Meta/Google/others ad SDK to spy on all my users. Maybe we should stop normalizing these behavior.
Snarky comment aside, Python is definitely *not* a "live system". If you had worked with such system before you'd know the world of difference between a version release of "stable" software versus a live platform that cannot fail.
Indeed these voices will drive some sales away, but unless other options are competitive with Bambu's offer, they still sell some of the best price-performance-reliability ratio printers on the market, and that's really attractive for the average buyer.
Most commenters here will value the openness of Prusa, but most lambda users will have limited budgets that Prusa does not cover. The U1 is a great attempt at taking on BambuLab head front, with interesting features at a reasonable price point.
In the end, a lot of people (including here) are using an iPhone even though it's locked down to a higher degree. Some people like a walled garden, some don't care.
I'm not against rewriting it in Rust because I believe it really may help in certain class of bugs, but indeed it should not be replacing the old version instantly for that reason. Both could co exist, even tho you still need some guinea pigs to test it out and find issues.
Other than security, Rust brings major improvement to the tooling and may help bring fresh members that wouldn't want to contribute to C code. I understand why some projects go that route
How many CVEs in coreutils over the years? The project has the advantage of being old enough for them to be fixed. Call me when the rust rewrite has been there that long and still has more CVEs than the GNU counterpart.
Good joke if you think more than 1% of their customer base will care about that.
Bambu is not (never has been?) targeting 3D printing hobbyist but everyday people; and for them cost/reliability is more important than running your custom slicer. Until there is a serious competitor that has a polished and cheap printer, Bambu can alienate all of the open source community and still be fine.
It's a toggle you set in the printer directly, nothing is circumvented. Only the access through their cloud service is impacted, but the printer works locally like any other.
Yes and the result is these databases got forked, and the community got rightfully mad.
But other databases don't need it, and stayed truly open source, because their business model doesn't rely on being the only hosting provider.
> You didn't incur any costs in producing the thing you're selling, duh!
Indeed, you gave it away for free, saying I could sell it... It doesn't take a business genius to know AWS can undercut your hosting services.
It goes to show that most of these companies don't really care about open source. They cared more about making money and open source was a useful facade to get people to contribute for free.
Because people are saying the same shit about the previous controller, when it's verifiably false. The new controller operates on exactly the same principles
Prusa is also pursuing patents (they say it's because of Bambu but lol), and they are not releasing their firmware sources for recent printers.
Bambu did not close the tech they used to make their printers. Others (including Prusa) are making CoreXY and they 100% also benefit from the RnD that Bambu did (either hardware, or the slicer (without which Orca would not exist in its current form)).
Bambu just made better products for cheaper and Josef got mad. But I'm certain that Prusa could compete had they focused on making price-competitive polished printers, and not focus on $5k monster printers for enterprise.
Why isn't this a problem for other databases then? I'm sure most cloud sell some MariaDB services. Why would they be able to profit from it?
It's because the business model for ES is direct competition with AWS and others, and they got out competed. So they had to play licenses games to try and level the field.