Chronotope’s avatarChronotope’s Twitter Archive—№ 86,508

      1. These moments all seem inevitable. Oh, Chrome will be on top forever. But remember all those hip web devs making Firefox only sites back in the day? Hubris leads to downfall. Chrome's wings are melting as we speak. theverge.com/2018/1/4/16805216/google-chrome-only-sites-internet-explorer-6-web-standards
        OpenGraph image for theverge.com/2018/1/4/16805216/google-chrome-only-sites-internet-explorer-6-web-standards
        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 3 Favorites Mood +2 🙂
    1. …in reply to @Chronotope
      IE6-only sites -> Firefox-only sites -> Chrome-only sites. There's nothing new under this sun.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
  1. …in reply to @Chronotope
    Gotta say though, the irony of someone from Mozilla complaining about this is *high*
    On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets Mood -3 🙁
    1. …in reply to @Chronotope
      Don't build websites to a browser. Don't support single-browser functions by using them. Be a good web developer and build sites for the web as a universal viewer-disinterested platform. All sites should work on all things that follow standards at all times.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets ❤️ 1 Favorite Mood +1 🙂
      1. …in reply to @Chronotope
        And when a browser does stuff off-standard *cough*firefox*cough* you call them out.
        Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood 0
        1. …in reply to @Chronotope
          What people forget is that when you build to a browser, you're really building to a *version* of a browser. Even that browser may not work with your site 10 or 20 versions down the road. Build websites that work on an off-brand Android phone, a TV, and any damn browser you try.
          Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood -3 🙁

Search tweets' text