5 ms·

As an example, anyone remember the glaring indexedDB and flexbox bugs in Safari?!

• Klathmon 9y ago
  That's my issue. I've basically learned (as a developer) to not use any new features in Safari until the version after they come out. IndexedDB was broken so badly it literally wouldn't work, flexbox is much better now, but I wouldn't have called it "supported" by safari for a while, and now while their WebRTC APIs work, they are really flakey and have a lot of extra "restrictions" tacked on that aren't really explained anywhere (like they won't work in a WebView, or if the page is bookmarked on the homescreen). I like what they are trying to do, and I absolutely think there is a place for a browser that is fast, low resource usage, and more stable, even if it means it's single platform, slower to add features, and doesn't have as many customization options. But Safari is falling short of their goals while still having those downsides and on one platform is the only browser that is allowed.