That assumes dev resources are limitless. And for a company the size of proton that’s certainly not true.
They can only have X amount of devs. So how they allocate them says a lot.
Also given that most complaints I’ve seen at the top are about specific missing features for ages, I think it’s safe they’re putting their eggs into too many baskets.
That assumes you don’t value your time spent dealing with troubles that come.
Like the other person said, it’s fine if you don’t, but for me it’s worth a little upfront cost to have to deal with less ordering new drives, putting the drive in the server, monitor rebuilding of the array, ect…
None of that is an excuse for lack of proper backups. Because even new drives can fail catastrophically.
Airbus. Bombardier has manufacturing plants in Canada.
So this was before airbus bought it from Bombarider.
The original deal was a 51% stake in the company with the option to buy the rest within a few years. This was in exchange for building the C series as it was called inside their US facilities. Since it would be American built, there’d be no import tariff.
Then when the deal settled, airbus very quickly chose to purchase the entire program from Bombardier. That’s the deal we know to get the A220.
Airbus already has an A320 plant in Alabama. https://us.airbus.com/en/airbus-us-locations#:~:text=The Airbus U.S. Manufacturing Facility,aircraft%2C producing 60 aircraft annually
That plant is why airbus was brought in on the Bombardier deal. It was originally to make the C220 in that plant to get around import tariffs.
Sync the internal drive cache with the disk. IIRC