• smileyhead@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    63
    ·
    1 year ago

    There is an issue with monoculture of rendering engines. Developers assume every browser have the same things implemented and start to build around this assumption. Also Google can dictate how the web looks like.

        • DrDeadCrash@programming.dev
          link
          fedilink
          English
          arrow-up
          11
          ·
          1 year ago

          You’re missing the point. Netscape implemented the html standard, they didn’t introduce new, proprietary “features” to gain that market share.

        • DrDeadCrash@programming.dev
          link
          fedilink
          English
          arrow-up
          16
          ·
          1 year ago

          There are two things to consider here:

          1. Adherence to Standards
          2. Creating artificial “feature” based defacto standards

          Chrome offers adherence to standards as one of their features. But it also introduces new features that look like standards, meant to increase profits for the parent company.

          • oyenyaaow@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Chrome offers adherence to standards as one of their features. But it also introduces new features that look like standards, meant to increase profits for the parent company.

            VB.Net was exactly that. Difference being Microsoft’s interest was locking companies and governments onto Microsoft’s enterprise products vs Google’s user tracking. Easy, quick internal web app put together in half a day? Would never work right on Netscape. It takes work to make them work to standards.