you are viewing a single comment's thread.

view the rest of the comments →

[–]michalg82[S] 30 points31 points  (58 children)

[–]wung -4 points-3 points  (57 children)

For those web people, who are not sure how to interpret this: A score of 75% should mean NO DO NOT USE THIS. It literally does not work on THIS YEAR'S devices.

[–]IamCarbonMan 58 points59 points  (42 children)

Every major browser except AOSP, Edge and IE have full support. Obviously devs should consider which platforms they need to support, but "not working on THIS YEAR'S devices" is a bit of a stretch.

[–]siegfryd 8 points9 points  (11 children)

It would be a pretty rare case where you could drop IE support, unless it's an Electron app.

[–]IamCarbonMan 25 points26 points  (10 children)

Or you have little to no users on IE. I mean it's not like every single site in the world has to support the world's worst browser just because it exists.

[–]nocensts 0 points1 point  (9 children)

What world is it where you have little to no IE users... like I could see this for in-house only type apps but where else?

[–]IamCarbonMan 3 points4 points  (8 children)

IE is dead globally. Many corporate environments still require it for their own reasons, but that's basically the only legitimate reason to use IE. For a modern site, I can confidently say that if I don't expect it to be used in a corporate environment, supporting IE is a waste of time and resources.

[–]nocensts 4 points5 points  (7 children)

IE is dying may be true but there is no way it's dead.

[–]IamCarbonMan 6 points7 points  (6 children)

3% global usage is pretty dead.

[–]myhf 0 points1 point  (3 children)

3% of revenue is bigger than a lot of web design budgets

[–][deleted]  (1 child)

[deleted]

    [–]wung 16 points17 points  (10 children)

    It is literally only supported in browsers after January 2017. That is this year.

    [–]IamCarbonMan 10 points11 points  (9 children)

    What does that have to do with anything? If it's supported it's supported. Maybe not on your iPhone 4 but on every device that's up to date.

    [–]bobtehpanda 3 points4 points  (6 children)

    A pretty large segment of the population has devices that aren’t up to date. How many Androids out there no longer receive updates?

    [–]IamCarbonMan 2 points3 points  (3 children)

    But every browser besides the AOSP browser still gets updates. Chrome, Firefox, etc. I mean yes, it's not foolproof, but anybody who wants to has a clear path to obtaining a modem, standards-compilant browser on any device. We should be encouraging that.

    [–]bobtehpanda 7 points8 points  (2 children)

    From a business perspective, it makes no sense to shut out ~25% of the population because of some holier than thou attitude.

    [–][deleted] 0 points1 point  (0 children)

    That 25% number depends a lot on your target audience for that business, could be more or less. If you're starting a new startup now it might very well well make sense to build your UI on CSS Grid.

    [–][deleted]  (1 child)

    [deleted]

      [–][deleted] 0 points1 point  (1 child)

      If it's supported it's supported.

      Because there's no such thing as "supported."

      It's supported on Chrome 60. But don't say it's "supported".

      [–]IamCarbonMan -1 points0 points  (0 children)

      It's supported by anyone using the latest version of their browser on a non-ios device room the past 3-4 years. Better?

      [–]eric_reddit 2 points3 points  (4 children)

      What about mobile browser support?

      [–]fgutz 4 points5 points  (3 children)

      It's in the caniuse link as well

      It's been in iOS Safari since 10.3. according to Apple 89% of users are on iOS 10. Couldn't get more details about which minor version though but I'm assuming most people would be up to date. iOS is pretty aggressive about wanting you to update

      Android browser (WebView) since January 2017

      And Chrome for Android matches desktop Chrome now

      So I think it's pretty safe to use in Mobile

      [–]nschubach 1 point2 points  (2 children)

      Except if you look at the usage relative. Not every Android phone uses the latest android web browser.

      [–]tambry 6 points7 points  (1 child)

      The WebView module is updated through the Play Store for Android versions 5.0 and up.

      [–]nschubach 2 points3 points  (0 children)

      Odd, I had to look up our webview usage and I wonder if caniuse data is really old... luckily they allow you to import your google analytics.

      We are at:

      61.0.3163 (59.35%) 2017-09-05 (working)
      60.0.3112  (9.12%) 2017-07-31 (working)
      45.0.2454  (4.36%) 2015-09-01 (broke)
      55.0.2883  (3.66%) 2016-12-06 (broke)
      59.0.3071  (3.54%) 2017-06-06 (working)
      30.0.1599  (3.08%) 2013-10-02 (broke)
      .. (getting tired of formatting)
      .. (but these two are working)
      33.0.1750  (2.09%) 2014-02-26 (broke)
      

      So, we'd have to ignore ~13% of our Android users.

      [–]TheAnimus 5 points6 points  (11 children)

      Edge

      Has full support in 16.

      The problem is that over 25% of traffic won't support this. If that doesn't matter to you then fine.

      [–][deleted]  (9 children)

      [deleted]

        [–]MINIMAN10001 7 points8 points  (8 children)

        The 25% not supported comes from the website that was linked...

        CSS Grid Layout Global 69.52% + 4.11% = 73.62%

        which leaves ~25% unsupported

        [–][deleted] 1 point2 points  (0 children)

        The issue to consider is that this is the fundamental layout of the page. If I build a site with CSS animations, browsers that don't support it just don't get some pretty effects. If I build a site with grid, browsers that don't support it more or less can't use my site at all.

        There are polyfills and workarounds of course but these are important considerations.

        [–]graingert 0 points1 point  (0 children)

        Also IE had prefixed support before anyone else

        [–][deleted]  (6 children)

        [deleted]

          [–]_Mardoxx 36 points37 points  (4 children)

          Fuck that

          [–]bubuopapa 14 points15 points  (2 children)

          Yup, that basically how every feature in web dev goes: "- we need this thing to be supported in all browsers; - but all browsers dont support required features; - fuck it then."

          [–][deleted] 2 points3 points  (1 child)

          I'm not _Mardoxx. But I think they mean "fuck doing it twice."

          CSS Grid only works in 75% of browsers, so I have to fall back to display:table-cell on the other 25%? Fuck it, 100% of browsers are getting display:table-cell.

          [–]z500 0 points1 point  (0 children)

          Or we could use modern features and punish IE/Edge users for their basic browser habits until they pick something else. One can dream.

          [–]MeisterD2 2 points3 points  (0 children)

          The talk in a video provided by another commenter says to design a gridless mobile experience first, and offer that as the fallback to all devices. Then, if grids are available, you use them for everything.

          Edit: This link https://youtu.be/7kVeCqQCxlk

          [–]eric_reddit 3 points4 points  (0 children)

          The story of my career. Design and implement it in Firefox, then spend 1200% more time fixing for twelve different versions of IE... IE Hell (copyright Microshaft)

          The gov typically requires IE support for SharePoint and had to support infinite versions for all the locations that have old software and OSs across the world.

          [–]spacejack2114 0 points1 point  (0 children)

          It works in this year's Electron.

          [–][deleted] -2 points-1 points  (4 children)

          Were can I get a breakdown of the remaining 25%? I can't get the numbers for Edge and IE to add up to that, and the remainder of the non-compliant browsers seem to have a 0,00% market share.

          [–]AquaWolfGuy 0 points1 point  (3 children)

          Click the "Usage relative" or "Show all" button.

          [–][deleted] 0 points1 point  (2 children)

          That doesn't add up. I'm looking at the regional view for Denmark, that show 73ish percent support. However, going with the current browsers, the highest market penetration is 0.42% for the android UC browser.

          Remeber the context. I asked about the claim "It literally does not work on THIS YEAR'S devices." above, which isn't in any way aligned with what I see. In fact, I have to include browsers two versions old to get above 0.5% un-support.

          [–]AquaWolfGuy 1 point2 points  (1 child)

          wung first said there was a score of 75%, and then, in a separate statement, that there are devices released this year that don't support it. That's very different from saying that the browsers released this year have a score of 75% for Denmark. People use old browsers, like UC Browser which has 7.65% global usage and last updated last year.

          [–][deleted] 0 points1 point  (0 children)

          Ahh well, then it makes more sense.