Was surprised this comment was this far down. I re-read the YC ask three times to make sure I wasn’t crazy. Dude wrote the whole article based on a misunderstanding.
I wont mention what company, but where I work we've spent about 6 months now with an entire dev team hammering their heads against a wall trying to port our extension to MV3, because the alternative was to lose it entirely at the deadline.
Hacks, workarounds, bad docs, and lately, Google pops up to tell us OSD is kinda sorta a thing you can use, but clearly it's at a basically alpha level of maturity. This latest announcement might seem like a reprieve, but it's even worse than before for us, because now it's clear that OSD is a temporary measure, and now we have promises to fix the actual issues in the future.
As a manager I have no idea how to proceed. Do we solider ahead with OSD like we planned? Wait for them to fix the core issues? We have so little trust in Google fixing things, and a great deal of confidence in them making things worse at this point. If we commit to OSD we might be looking at doing the same level of work again, when they fix the core issues and deprecate it. If we wait for core fixes, we might not get the work done before a nebulous future deadline that could drop on us at any moment.
Google has caused us to burn an absolutely incredible amount of time and money with this. Believe me, we're are footing the bill, and have been for some time now.
I’d like to add RockAuto as a peer to McMaster. It’s auto parts, and somehow uglier than McMaster, but damn if it isn’t the fastest no nonsense website I’ve seen for parts.
I can drill down to a specific part for a specific car in seconds, and see pics of the product, part numbers, specs. It’s lovely.