It boils down to
- Labor relations (unions in Arizona pushed back agains Taiwanese workers build the factory)
- Local partners (Denso/Sony and Toyota investing in Japanese project, TSMC on its own in the US)
- Subsidies (Japan delivered on promises, US didn't)
- Ambition (12nm-28nm in Japan, 4nm in US)
It seems the US gov is not very serious about it while Japanese gov surely is. It sounds self-inflicted.
(edit: formatting)
Free market, it's valued more somewhere else. Seller sells it there. Simple as.
With most tech that I screw up I assume that "I wasn't using it right" but with GraphQL I'm not sure how anyone could. The permissions/auth aspect alone is a nightmare. Couple that with potential performance issues (N+1 or just massive amounts of data) and I want nothing to do with GraphQL anymore. Everything we attempted to fix our permissions issues just caused more problems. It would break existing queries and debugging GraphQL sucked so much.
If you only live on the frontend and someone else is responsible for the backend GraphQL then I understand why you might like it. From that perspective it's amazing, you can get as little or as much as you want with the specific fields you want. No waiting on the backend team to write an endpoint. However even then you end up saving queries as files or abstracting them (maybe IDE support has improved but it wasn't great last time I was using it ~5 years ago) and now you just have REST endpoints by another name.
At one point we considered whitelisting specific queries and that's when I knew we had gone too far and made a mess for ourselves. If we had taken the time to just write REST endpoints instead we would have gotten way more done and had way fewer grey hairs.