They aren't allowed to tell you anything.
They aren't allowed to tell you anything.
I had to check that this did come out of CloudFlare.
After the 1992 Consensus [1], the Taiwanese government still considered the Mainland its territory (again under a One-China Interpretation), but also acknowledges the CCP's interpretation of One-China. In practice, this meant they officially abandoned plans to re-take the Mainland, and focus on maintaining the status quo of peace and stability.
Interestingly, the Taiwanese government also used to lay claim to Mongolia in addition to the Chinese Mainland.[2]
[1]https://en.wikipedia.org/wiki/1992_Consensus
[2]https://www.taipeitimes.com/News/feat/archives/2024/08/25/20...
It's whose government will get to run the whole thing.
US has become less dependable but a lot of countries still depend on US maybe less but not as allergic as depending on China.
That 5%-20% is worth it now because no one else can fabricate competing chips. In a competitive market, 5%-20% can be the difference between having the price edge or not. I understand why the USA wants TSMC to manufacture outside of Taiwan, but perhaps it makes sense to move it not the USA but, say, Mexico?
Chinese car companies seem to be slowly but surely rolling American car companies in international markets with great value at low prices. The move in this market evidently isn't to move manufacturing away from Mexico at a 5%-20% increase in price.
In the chip market there's less immediate competition, but I can only imagine it'll come. Hopefully economies of scale would have removed this extra 5%-20% by the time China catches up?
Japan, Korea, Taiwan, and other countries even Philippines and Vietnam don't want to depend too much on China. A lot of island disputes and so on and so forth.
My guess right now is that China will never catch up because Europe, US, Australia, and many other developing countries will avoid depending on China critically. This doesn't mean 0% would buy from China but it'll never become a critical dependency.
Odd UX that can't be configured (and no idea why). For example, if you touch the power button, it'll unlock and wake up the phone. There's no way to turn that off and require a click. Other android phones can but not minimal. like what the hell was going through their decision making process?
Debugging is a nightmare because it refuses to even compile if you have unused X (which you always will have when you're debugging and testing "What happens if I comment out this bit?").
The bureaucracy is annoying. The magic filenames are annoying. The magic field names are annoying. The secret hidden panics in the standard library are annoying. The secret behind-your-back heap copies are annoying (and SLOW). All the magic in go eventually becomes annoying, because usually it's a naively repurposed thing (where they depend on something that was designed for a different purpose under different assumptions, but naively decided to depend on its side effects for their own ever-so-slightly-incompatible machinery - like special file names, and capitalization even though not all characters have such a thing .. was it REALLY such a chore to type "pub" for things you wanted exposed?).
Now that AI has gotten good, I'm rather enjoying Rust because I can just quickly ask the AI why my types don't match or a gnarly mutable borrow is happening - rather than spending hours poring over documentation and SO questions.
Go people will yell at you because you aren't using the right tool.
Yeah, Go is too rigid with their principles.