yeah, a lot of PR effort for Bambu while the reality is slightly different.
An example: they say: we didn't patch the security hole (the user agent "chech") because the user experience would have been affected blablabla...
Well, they introduced this security hole on linux BECAUSE they deployed the new mandatory network "plugin" (that you are forced to use because: it's automatically installed and it's mandatory to print even locally) without providing a working solution for all their linux customers when deploying it.
Yes! They didn't implement a real authentication solution for their own linux implementation AND they didn't answer to their linux customers who had the software broken for MONTHS.
And them providing this user agent hack solution months later allowed anybody to understand how it worked without retro engineering their network plugin (something the article forgot to mention but it was the main attack vector of bambu against the developer threateninghim to go to federal jail, something they also forgot to mention).
Great user experience mindset here. Breaking their printer to introduce a mandatory connectivity plugin (reminder: linux is officially supported on the marketing pages) and threatening those who try to fix it using just what the license allows them to do.
I suspect the DDOS attack they had on their cloud service is more linked to their change of mind regarding this mandatory network plugin.
It could be all the linux client trying to download their network plugin but failing and retrying in loop. That wouldn't surprise me following the user agent choice.
Or people unhappy. After all, they changed the terms of the contract after users bought the printer. Really a Dark Vader style of user experience here!
If you want to avoid this kind of amateurish/parasitic behavior, buy the original: Prusa.
I've one printer from them since many years that I upgrade each few years. Currently, I'm waiting for a sale for the upgrade kit to the Core+
Coding is the easiest part of the job and do not represent the main people activity.
Looking at the number of lines of code and thinking "they are only doing that" is like looking at any Mozart cues and thinking "he spent years to fill 50 pages of black dots?".
Coding is like creating music. It's not because you can write lines of code that the result will be a working solution.
You need to know your activity very well to be able to get the best from all the instruments you have in your hands.
Before coding any line, you had to THINK about the solution, find the best architecture, how to implement it without impacting in a negative way the product, detect the potential side effects, how to test in all the possible scenarios, how to maintain it, etc.
What you pay here is knowledge, experience, architect skills, coder, tester, troubleshooter, project management, devops, etc.
You pay highly skilled people who have the responsibility to not screw up all the servers infrastructure of the world, the brains of aircraft, cars, manufacturing tools, etc... And you don't want them going elsewhere as the knowledge ramp-up of any newcomers could take years.
This is where the salary goes. People brain.