Why does a CoC have anything do do with a maintainer stepping down due to a technical disagreement?
And the way you word it makes it seem like you think CoCs are bad or “forced”; I don’t particularly want to engage there, but I’d encourage you to reflect on why you think that.
As someone that has lived in several countries, and currently in Canada, I will respectfully have to disagree both about your opinion of the CBC and beliefs about government intervention. Some parts of Canadian local/provincial/federal government seem deeply dysfunctional, but some are extremely helpful and better than I’ve seen elsewhere.
Tell that to companies doing extremely large-scale machine learning. Or any cloud infrastructure provider. Or CDNs. Or literally any video production company that owns a render farm. Or any company doing large-scale media transcoding/streaming.
Maybe "don't have thousands of servers" is just a bad take :)
This is part of what makes this class of bug so bad; it's not something you can "fix" at the IDP without doing exactly this. The issue occurs when a Service Provider (SP) is misconfigured, and in many cases the IDP doesn't actually get any sort of feedback that would let them detect the issue.
Shout-out for "AutoSpotting", which transparently re-launches a regular On-Demand ASG as spot instances, and will fall back to regular instances:
https://github.com/AutoSpotting/AutoSpotting/
Means that you can be reasonably certain you'll never run out of capacity unless AWS runs out of every single instance type you have requested, terminates your Spot instances, and you can't launch any more On-Demand ones.
(and even so, set a minimum percentage of On-Demand in AutoSpotting to ensure you maintain at least some capacity)
I really like chi[0] - I think it strikes the right balance of being small and understandable, but also solving common problems (e.g. nested routes, URL parameters, etc.). It also uses standard Go conventions, so it's very interoperable and would be easy to migrate away from, if necessary.
Mind providing more details on your setup here? I tried throwing together an overlay network using OSPF, but never really got it off the ground. I'd love to hear what you've got here!
Your sign up JS is broken - I just tried to enter my email and got a "TypeError: undefined has no properties". Looks like a cool project, though - I've wanted something like that for a while :-)
From that page, it looks like the price of the washer, adjusted for inflation to 2016, is $1756.12. A comparable washer today, from Sears, appears to be somewhere in the $400 - $600 range, or about 30% as much as it used to cost.
I mean this in the nicest way possible, so please don't take this as anything personally directed at you, but: any employee of Uber that feels strongly about this should find another company to work at. If you're working in tech, in the current employment market in the Bay Area, finding another job is not hard. Not easy, both in the sense that leaving a job can be scary, and that interviews can be draining - but doable.
There are other companies out there that solve interesting, challenging problems and don't have this toxic culture. There are other companies with talented people. And if enough of your coworkers disagree with Uber's culture, policies, etc., then the talented, moral people that you work with at Uber may even come with you.
The only way Uber will ever pay attention is if it affects their bottom line. Employees leaving, or people turning down offers is, person-for-person, one of the most impactful ways to do this.
