But now for a mostly different reason: web standards. Chrome is usually leading the pack with implementing new Javascript features, CSS features, performance op

But now for a mostly different reason: web standards. Chrome is usually leading the pack with implementing new Javascript features, CSS features, performance optimizations, etc. Browsers with weird quirks or that aren't properly written to spec (eg: older IE versions of Flexbox) won't work as well. Some developers, such as myself, think users should be updating their software if they really care that much about some things being broken. If my Javascript uses .map() and your browser doesn't support it, too bad. I'm not including the polyfill for everyone just because some small minority of users need the polyfill. Those users can update their browser. Resources spent trying to support people who refuse to update could be better spent on providing more benefit to everyone else. With rare exceptions, anything that "works best in Chrome" works just fine in Edge/FF. Usually Safari is the new IE6 with everything being broken. In the 'What's Next' section: *>Browser Compatibility Currently the database UI works fine on Chrome, but has issues with Firefox and Safari; we’re working towards supporting all major browsers.*