The high numbers here are eye-opening, but the article doesn't shed any light on the process.
I'm left with the feeling that opening a restaurant is hard, but there is nothing to chew on in terms of improving the situation as a citizen or interested party.
Not having played with SIMD much myself, does leveraging these instructions for an intensive operation like a sort push other workloads out of the CPU more aggressively than operating on 32 or 64 bits at a time would?
In other words, do you have to be more careful when integrating these wide operators to preserve some resources for other operations?
This isn't how scaling works though. Across all applications the hot data growth outpaces the cold.
So if you're designing capacity for exponential growth, the future point at which you stop experiencing exponential growth and only have to worry about roughly linear growth is a much easier problem to solve.
Are you more interested in fixing a process or fixing the problem?
Sending in-product feedback certainly could work because it's more likely to be seen by product management as it continues to roll in.
Support-driven product change requests are well intentioned but generally break down as a process internally. The working knowledge base and incentives are not properly aligned.
I think you're spot on. Self driving software seems to me like it will handle the vast majority of driving situations much better than humans could within the 5 year horizon OP is asking about.
I'm left with the feeling that opening a restaurant is hard, but there is nothing to chew on in terms of improving the situation as a citizen or interested party.