The West forgot how to make things, now it’s forgetting how to code

Suppose someone new made a better mobile OS than Android. What would happen?

Google has convinced a lot of third party apps to use their anti-competitive attestation system that has no real security value but makes it so those apps won't run on a competing operating system even if it implements all of the same APIs, so it immediately has a major barrier to gaining traction. That should be an antitrust violation.

Then the incumbents would copy any innovative features the new OS has so it no longer has an advantage. On paper this is what the patent system is supposed to prevent, but in practice is does the opposite. If you as a practicing entity tried to sue a major incumbent for patent infringement, they would counter-sue and have an arsenal of thousands of patents that could keep you bogged down in litigation for years. Just the cost of litigation could bankrupt a smaller company even if they won, and there is enough ambiguity in the system that they're pretty likely to lose when the incumbent only has to find one patent out of thousands they were unintentionally infringing, or a court is willing to enforce one that ought not to have been granted. So then everyone has to file a bunch of patents for the purposes of mutually-assured destruction and can't really enforce them, which favors larger companies that can afford the overhead. It certainly doesn't protect the little guy and we would be better off without them.

Your suggestion is also essentially unworkable. NFL teams all have the same number of players and play the same game. Amazon and TSMC each have a very different business and largely aren't competing for the same people. Does Garmin get the same number of picks as Foxconn even though they don't employ nearly as many people? How many picks does a startup get? Do we count Apple as doing poorly because the gross margins on hardware are lower than they are on pure licensing, or Nvidia as doing poorly because they have higher margins but lower revenue? How are we accounting for engineers in other countries? What about engineers in China who work for companies in China who are contractors for international companies? What if a corporate contractor has more than one corporate customer? How do we account for open source? How do we distinguish engineers from IT staff or research mathematicians or prevent companies from giving willing workers a job description that doesn't match the work they're doing?

It's also probably worth pointing out that systems like that are essentially price fixing schemes by the industry to pay workers less than they would otherwise be able to get if other companies weren't prohibited from outbidding them for talent.

On the one side, it has succeeded at reducing costs, which has indeed given rich societies unprecedented access to consumer goods.

On the other, it has outsourced from us both jobs and knowledge, which has resulted in higher unemployment and dissatisfaction, with as consequences the political dominoes we see falling internationally. That and the shoddy US health system (which the rest of the world seems to have decided to follow, for some reason).

And there is the small fact that we're in the process of optimizing the planet to death, and that not-so-rich countries (as well as formerly-rich ones) have starved to death for this high standard of living.

So, let's appreciate our standard of living, but not assume that it's necessarily a good thing in the grand scheme of things.

how can you tell?

Exactly. In direct contrast to this would be how Xerox and Bell funded laboratories just to pursue knowledge, without demands of profit. They ended up creating incredibly profitable things when driven my knowledge, and not profit.

I also read a book about math where the author argued that while the Greeks were driven to pursue truth for truth's sake, they ended up being far more productive and innovative. The Romans who were more driven to work for solutions to immediate practical needs, ended up being not so productive and innovative. He used this as a defense for efforts in pure math that seems to have no immediate application but ends up being massively, surprisingly powerful and productive for practical applications down the road. I think the same could be said for software development focussed on truth and correctness, rather than immediate productivity.