and competition is healthy anyway, even for governments. That transfers of money in the US are relatively slow and relatively expensive is a technical issue for the FED to resolve; already a solved problem in the Eurozone.
i sometimes go to my local library (in a big European city). The computer science section has a lot of "for Dummies" books or titles that are very specific to a certain language version or framework (java 6, Symfony 3). Most of those can go straight to the trash. The many timeless books that exist are far and few between.
not quite - you have to think like a government. If people get paid less, the people who finance a given company get to keep more money, it might also be cheaper for consumers. The government has its hands in every stage of every economic interaction. What's "lost" in one area is made up in another. Even a drug dealer has to go to the gas station for example.
what's fast really depends on lot on what you are building - without more details about the challenge at hand any statements about performance are unhelpful. A huge backend system? The logic in a toaster? A space ship?
you have picked up so much meta knowledge (debugging, testing, build optimizations), domain understanding and soft skills that making the switch might be less tough than you think. Plenty of coins in Rust land, too!
No, I was thinking 'less mature web libraries' for Go. It's hard to talk about groups of languages in broad strokes when there are various tradeoffs and each language has its own strengths and weaknesses, and I painted two possible weaknesses broadly across several languages that don't strictly apply to all of them.
