3 ms·

And to generalize, I'd say that... "There is an imperfect existing solution, with a problem, therefore we will ban the existing solution and move to a new, bet

by ethbr0 4y ago

And to generalize, I'd say that... "There is an imperfect existing solution, with a problem, therefore we will ban the existing solution and move to a new, better one" ... should require extraordinary certainty in completeness of ones new solution before banning the previous. There are very few times when the legacy method should be deprecated, and Google is the poster child of someone who shouldn't be trusted to recognize them. (Looks pointedly at Chrome mv2/3 hubris and implementation clusterfuck)

AdamJacobMuller 4y ago
> Chrome mv2/3 hubris and implementation clusterfuck I'm not sure why you think MV3 is a clusterfuck, it seems like it's doing exactly what Google wants. If you're confused by that, remember, you're the product, not the customer.
- ethbr0 4y ago
  Assume I'm talking about something deeper than generic HN cliches. ;) Pushing an implementation cutover by +6 months, and changing it from a hard to a soft date, because it has so many unresolved issues, incomplete APIs, and angry developers seems a fair definition of "clusterfuck."
- xg15 4y ago
  At this point I'm not sure if this is cynicism or a legitimate opinion.