4 ms·

> It's also the bane of my existence as a web developer. I would say as a Chrome developer then.

• soperj 5y ago
  Thanks for making this personal. I wouldn't have any issue with Safari at all if I was just a chrome developer would I?
  • eitland 5y ago
    The problem was people pretending to be web developers but only testing in IE. Being IE only made life a lot easier. Same today. Some people think it is OK to test only in Chrome. That lets one get away with a lot of bad habits. Dealing with different browsers is part of what makes one a competent web developer.
    • soperj 5y ago
      The problem with their comment is that they're too busy dunking on people. I do deal with different browsers, hence why I get headaches from Safari. If I didn't, I wouldn't complain about it. I've been a web developer for a long long time. I know what a pain IE was, and I'm just experiencing it all over again with Safari, although they've gotten better lately.
      • tarsinge 5y ago
        My comment was maybe a bit provocative but you didn't just say Safari had a few quirks (like the slow release cycle for bugs like the recent ones with LocalStorage and IndexedDB that is a pain), you said it was your bane. That usually mean using Chrome as the main development browser and waiting years for new experimental API to be (sometimes) implemented in other browsers, particularly Safari. In that case like the parent said the pain is more similar to the one a IE dev would have experienced back in the day (early 00's, not late) when some IE specific advanced features would not have been widely available on other browsers.
        • soperj 5y ago
          No, it's the bane of my existence because of bugs, on stuff that people actually use, like flexbox. I use firefox for the record. IE devs didn't give a shit about any other browser, and never had a problem with using the IE specific features because of that.