First of all. The comparission to the cars is not very suited since the affordmentioned "small US cars" are in essence re-badged cheapo Korean cars. These are build by (a few) underpaid workers under control of one rich bastard and his (literally) robots.
So in that respect "the remaining developers need appropriate level of investment to enable them to hire the necessary programmers" is stupid because these "necessary programmers" want bucks for their efforts. I doubt that UK software developpers are as underpaid as korean factoryworkers.
You simply can't compare this. Besides all the electronic gimmicks don't make up for a bad ride. Japanese cars are still way better than cheapo korean s*** (even after all those years). So the only reason ppl buy these cheap cars and computers is that they simply don't have the money anymore to buy a decent stuff (but still don't want to loosse on so-called luxury). No wonder if you see the wages of ministers and politicians.
As for the office. It'll NEVER work because Windows (because of Microsoft cut-throught mentality towards competition) Office has one tremendous advantage nowadays.... Universal compatibility. The only thing we have that is universally compatible is bitmap-formats and draw-vectorimages. Thanks to AW-viewer AW-vector format is at least viewable by more users than the few Artworks owners but IMHO its still a wrong move. CC should have worked with Acorn to adapt the draw format as basis for Artworks files (and Acorn should have been more open towards CC to assist). Documents are NOT exchangable between RISC OS programs at all. This is a complete dissaster. The same applies to database and spreadsheet formats. And NO I'm not happy with "RTF" as an exchange format, because it's useless. A fact I have mentioned YEARS ago (along with other things).
The problem is that a lot more ppl at the sideline see this too. But they are not in capacity to actually do something about it. In fact those "leading" the RISC OS community should rather pay US, users/customers/whatever, consultancy fees.
What we need is a clear standard way of developing things. To define OWN standards and STICK with them. Make these universally exchangable on RISC OS machines (at least) and THEN we can start building applications around them. THEN and ONLY THEN you can mix match applications and talk about an "suits". Once that is accomplished you can target the outside as a unified platform with an internal universal exchange file format amongst ALL applications. Then at a later stage we can adopt alien file formats to exchange data to alien platforms. Or use these alien formats as basis for our own for all I care. But we URGENTLY should clean up our mess before attracting anyone else!
P.S.: I undoubtly stepped at someones toes. Appoligies for that. This is NOT a personal attack so don't "act" being offended.