• mind@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    5
    ·
    2 years ago

    That’s not the same.

    Microsoft was hostile to web standards and would not implement W3C recommendations in Internet Explorer, which meant most web devs would be wasting their time implementing those standards since almost all users were on IE back then.

    Chromium actually does follow standards, and has adoption through voluntary downloads rather than by being preinstalled on the monopoly OS.

    • DrDeadCrash@programming.dev
      link
      fedilink
      English
      arrow-up
      15
      ·
      2 years 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
        ·
        2 years 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.