the reality is that you can write very safe C/C++ code if you want to.
You could write safe C too if you want to. You could write safe assembly too if you want to. Unfortunately real world code is replete with errors caused directly by C++ language issues. And even if someone might strive to write safe C++ the compiler doesn't give a damn if it is or not. It might compile because it's safe. It might compile despite being unsafe. Forgot to lock that resource properly before accessing it from two threads? Storing a reference to something deleted elsewhere? LOL C++ doesn't care. Perhaps that is why there is an extremely lucrative after market of static analysis tools because the language sucks.
What Rust offers is the idea that you can achieve perfect memory safety without sacrificing performance. In practice, this is much less useful and bit based on exaggeration, but it makes for an excellent sales story.
It doesn't promise "perfect memory safety". What it does offer is a compiler that strictly enforces ownership and borrowing and will fail with a useful error message rather than allow the error to crash your code at runtime. Any programmer worth their salt would appreciate catching issues early on than suffering the consequences later.
But maybe you love it when your code has some random crash and it takes you hours or days to discover what the cause is especially when it was a pissed off customer who first found it. Ah but you write safe code so that never happens to you and if it never happens to you it must never happen at all right?
They would have been better off defaulting to LAN, but offering cloud for people who really wanted it. Maybe they could even have charged a $ amount for it, or bundled it up in some kind of subscription service that included some tangible benefits like free / discount filaments & parts, print farm analytics and other stuff.
As for the mobile app, cloud shouldn't be necessary but I assume they thought the phone and printer could be apart on different networks so they used MQTT or some other pub sub bridge to send messages between the printer and app.
So a saner course of action would be: "hey we can't continue to support cloud unless you pay us but we're leave LAN functionality alone". Even better: "hey we can't continue to support cloud unless you pay us, but here are the APIs if you want explore your own choices". Even better: "And we'll put the boot loader keys and sources in escrow just in case we have to shut services down entirely".
The issue for Anker or any other company trying to enter the market is that you'd have to produce an *exceptional* printer to stand out from all those brands. That's the reason Bambulabs is ascendant right now because their printer offered a lot of bang per buck in a reliable package and it generated buzz. Anker's printer offerings were fine but they were just another bed slinger in a crowded market. If the choice is a Bambu A1 for $399 or a Anker M5C for $399 then the Bambu wins. I note that Anker are on a firesale since this announcement so perhaps this is a good time to pick it up a cheap printer, but ordinarily... not so much.
And if people really do need better range then battery tech is only improving - there are cars right now with 400+ mile range and plenty more in the 300+ mile segment. As battery energy density increases and new chemistries appear I expect that EVs will diversify even more to provide what people need from their cars.
Toyota has been doing this bullshit for years. "Oh solid state is just around the corner and we're testing it so better hold off buying that EV you're after because it'll be obsolete soon *wink* *wink*". solid state battery.
Even if there were a viable, production ready, solid state battery announced today it would take years for that to translate into actual production because an entire supply line, infrastructure and factory would have to be built to manufacture the thing.
Always draw your curves, then plot your reading.