5 ms·
Which is a really good argument for never developing for the Google eco-system. Because you can't afford to invest in a platform where if something goes wrong y
by adamc 10y ago
Which is a really good argument for never developing for the Google eco-system. Because you can't afford to invest in a platform where if something goes wrong you're just f*cked.
- pyvpx 10y agoto be fair, for some parts of the eco-system, and for some values of investment, you can pay for support.
- malka 10y agoAgreed. At least on other corporate eco systems (Microsoft, Oracle, etc.), if you are a paying customer, you have great support.
- colemannerd 10y agoAbsolutely! You only have to use 10 year old technology for that support.
- throwanem 10y agoGreat! It's had time for a lot of the bugs to get knocked out, and most of the rest to be well enough known for fixes to be pretty solidly understood.
- Touche 10y agoPrecisely why I develop for the web.
- Merovius 10y agoYou are oversimplifying. There were multiple stages of things going wrong and there is no system where things can't get wrong to the point where "you're just fcked". What do you think how many innocent people got put in prison with no avenue of appeal, for example? Even suing for your right won't guarantee you the correct outcome and at some point you'll exhaust your options of appeal. This person just won the unfortunate lottery that in a large enough sample there has* to be at least one person who gets treated unfairly. Plus, of course, they are butthurt over the fact that they don't understand how trademark works (I mean… honestly? How could they think that that rename would make it better?). It's not like they didn't get multiple levels of appeals by humans, they just didn't like the answer they got so felt more comfortable blaming automation.