and the spaceship tech owner can just use that money to build and implement clean energy solutions to revert climate change, and never really need to build the actual spaceships..
This is like asking if one would pay more taxes, where it is unclear how the tax will be used to improve common good.
I bet if you ask people if they are willing to pay $1000 dollars (financed as $40/m in 25 months) to secure a spaceship ticket to escape the failing earth climate (assuming the spaceship already exists), many people will happily pay it.
that is a classic textbook dynamic programming (or suffix tree, depends on the size of the set) problem. behind the puzzle, it is the thought about dividing one bigger problem into smaller ones, and hence solve them with code efficiently. maybe that does not sound too far from your day-to-day coding.
the site probably should have presented these puzzles from a different perspective, so that it is easier for people to recognize the message about what kind of programmer skills and mindset it is looking for.
Like which IP policy? Any specific policy document that you can point out?
China has been having IP laws and protection since around 1980, and China government never said once that stealing IP is okay. It is IP law execution and enforcement in China that is sub-par. Policing is sometimes hard.
Also, I believe the US really wants to treat IP as an "asset" rather than a "product".
hmm.. I was not aware that Russ used the word "showstopper" until recently in his tweets, and even if he literally used the word in the past, the word of the meaning was not delivered, reading from the post here.
That said, the dep people also made a similar mistake on not clearly confirming with Go core team that they had a chance to integrate dep into the official toolchain eventually. They wanted dep to be the thing, and they really thought that they were on the right track.. poor folks..
If Russ managed to influence the "problematic" group to do what he wants, rather than doing it by himself, he could give these people a meaningful place in the Go community. That is the gain. If that is worthy or not (comparing with discarding 2-month work on Russ's own time) depends on your own perspectives, and I am not sure what Russ thought or thinks. No matter how, it will affect how the community grows in the future.
So this goes back to the root issue about how the Go core team view its Google-external language community (or even more fundamentally, if they will be rewarded/recognized by Google if they did a good job on making the community happy). Specifically, do they want to carry the responsibility to deliver messages to the community clearly, at least to some certain extent? Opinionated is fine and firing users (e.g. users who think generics is a must) is fine, sometimes even preferred, but hurting people that were willing to follow and contribute might not be the best way to go.
I think the issue is that Russ should have clearly told the dep people that if the showstopper issues are not handled, then he will seek for some other solution, e.g. build one by himself.
However, what happened was that he told the dep people "I will build a dep tool myself to understand more on the problem details", which implies "after I understand more, I will come back to you and discuss more", but not "after I build the tool myself, I will just integrate my version into the official tool". For this part, Russ was not executing his own words, or at least delivered the wrong impressions. Maybe this result should be already well expected based on Russ's personality or how the golang team did stuff in the past, but many programmers are not that politically awareing..
It is not the technical result that the "vgo" solution kills "dep" saddens dep people. It is rather the form of communication: "vgo" stabs "dep" in the back, by emerging suddenly out of Russ's pocket, and essentially claims immediate victory using the power of the Go core team. When the vgo posts are out, and the vgo proposal is posted (and it is not really bad technically), there is really no effective way for the rest of the community to reject it.
Russ could have kept his words by going back to the dep people and told them about what he learned from writing "vgo", and then move forward with integrating "vgo" if a consensus cannot be reached. Eventually, Russ might just be able to get the same technical results as today anyways (but maybe with larger communication overhead).
What the dep people essentially says here is that, if Russ really wants, they can also implement exactly "vgo" from "dep", but they never got the chance.
fwiw, I maintain a website called smallrepo (https://smallrepo.com). It builds go language code together, and maintains an always buildable commit set as a "super repo". If you sync to smallrepo (rather than using go get), it can shield you from many unexpected build breakages.
You are justifying your fear of a rising power, as if you are threatened, and you have all your rights to fear. However, the truth is that the West is still arguably more powerful, where the Chinese people are the ones that have been living in this exact kind of fear that you stated for a very very long time. If your reasoning holds as a universal value for all human beings (but not just for you), then it is effectively justifying a historically less powered entity, China, now eventually becoming free from this threat, where the world becomes more equal and multi-tenant in power, and you should happily embrace it.
Maybe what you fear is not that you are threatened, but that your current way of threatening other people in the world is no more. What you fear is change.
And yes, you are stating the facts: one of the ugly parts of human nature.
Chinese people also feel threatened by the West, because they don't trust you. There's not much more to it. They fear that you might abuse your power or use it to destabilize China. There's a lot of hatred of China, and they don't want you to try and trample Chinese norms, culture, society... things which they care about and are deeply connected to.
That's not to say the West actually would do any of those things, the key point is the lack of trust, specifically trust that you would do anything to benefit Chinese people or protect Chinese or that you care about them at all. They don't trust you, and the specifics of what you could do to hurt them are not really something they consider (but as you, the West is already powerful, you have many more options... to the point where one day maybe be the Chinese are dwarfed again by the West, and have no ability to defend themselves should they have to.) The west is very scary to Chinese people.
an army of "toddler" developers can overthrow a single hero in terms of productivity, and using a "toddler" programming language makes sure that newly joined "toddlers" can understand (and also maintain or upgrade) existing code, so that the army can just keep growing.