That particular knife cuts both ways.
What seems to work: Geographically distributed but autonomous product-dev centers, with remote workers aligned within a certain timezone.
What doesn't seem to work: Outsourcing pure dev work to timezones with no overlap.
I don't believe the above will change even if things become more remote-friendly. Perhaps we'll see more dev centers pop up to service the needs / wants / cultural or language asynchronicity of a given region, but that would lend more toward expansion than cost reduction. This also resonates with the approaches being discussed that I've read and heard first hand from company leaders during COVID.
If there is no benefit for paying a premium why not go with the commodity? Why go with an outmoded restriction to only hire blacksmiths in bounds of the south side of the original city limits? (Because they didn't want to smell the smoke in the posh north side while requiring the smiths live within the innermost set of city walls so they were available during a siege).
Can't speak for Japan, but the tech salaries in the big cities in Australia and Canada are far more competitive than those in Europe.
The European tech industry is an absolute joke overall, and I say this as a European. It would take an utterly massive overhaul to correct without relying on outright Chinese-style protectionism, and as more companies move remote and snatch top talent in timezone-friendly countries, time is running out faster than ever.
Good luck to European leaders in responding to the question of "Why would I, as a European in Europe, work for a European 'tech' company for terrible pay, when I can work for a US or Canadian tech company remotely for far better pay, on stronger teams, while retaining the same benefits of living in Europe?".