I don't understand. Regardless of COVID, they always need to consider the impact on developers.
Like I said in my previous comment, the newly remote Chrome team may be facing many unseen roadblocks, but I expect that to be a temporal window of delay, after which the team should resume shipping, albeit at a slower cadence due to reduced productivity compared to normal-times WFH.
We always consider the needs of developers, but we also tend to ask a lot of them (new perf, security, capabilities etc etc) in more normal situations, but I'd add this is a highented situation for all users and develers where everyone is requiring information and access to services like never before it makes sense to be very prudent in all of our rollouts.
Whilst I love NFC API, it's not critical at this moment where as ensure there are no (or as rew as possible) regressions is.
Wrapping up, it's a massive mix of needs right now from our own teams and users alike.
I want to say that I appreciate your team's decision and I especially appreciate your personal effort to answer questions here in public. I'm sure it's frustrating when people second guess important decisions during a stressful time. Just want you to know I (and I'm sure many others) see your effort and appreciate it.
> I don't understand. Regardless of COVID, they always need to consider the impact on developers.
Sure, but that impact might be somewhat more... impactful right now. This isn't that difficult. If you're a FB user, you probably saw last night nearly all of your friends reporting that their posts were being flagged as spam yesterday. That's because a bunch of people were sent home and the automated system took over. Staffs are being sent home and their ability to work effectively is reduced. The prospect of breaking changes and new bugs in the world's most popular web browser could put more strain on already strained teams that are struggling to keep up with both their current working environment and new challenges as they respond to the public health crisis. Removing that as a factor is a net benefit for those teams and for all of their users.
Like I said in my previous comment, the newly remote Chrome team may be facing many unseen roadblocks, but I expect that to be a temporal window of delay, after which the team should resume shipping, albeit at a slower cadence due to reduced productivity compared to normal-times WFH.