• Kichae@kbin.social
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      Have you considered just forcing everyone to access your sites via Internet Explorer 5.5?

        • Cabrio@lemmy.world
          link
          fedilink
          arrow-up
          4
          arrow-down
          2
          ·
          1 year ago

          Ahh the old Nutscrape Aggrivator. Refused to update with Microsoft standards and spent the next 8 years being a pain in the ass for website compatibility.

              • martinb@lemmy.sdf.org
                link
                fedilink
                arrow-up
                5
                ·
                1 year ago

                No. I was just looking for an example of when Microsoft created standards for IE that other browsers could adopt, given that they were tied into IIS and undocumented in order to give them an uncompetitive advantage. Let’s also think about how they deliberately downgraded performance, or broke functionality on non Microsoft browsers, again for anti competitive behaviour.

                They were called browser wars for a reason, and Microsoft is very well documented indeed regarding their fuckerry. But you go ahead trolling.

                • Cabrio@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  1 year ago

                  Yes, everything you said is correct, ipso facto Microsoft won and was setting the standards at the time.

                  The competitors still had significant market share and thus their obstinance to follow the leader lead to a large portion of users that had to be catered to by web developers for compatibility due to corporate requirements for access to these market shares.

                  Thus because these competitors weren’t the key demographic, in the context of a developer, they were an additional burden due to the severe lack of uniform standards between major platforms.

                  • martinb@lemmy.sdf.org
                    link
                    fedilink
                    arrow-up
                    1
                    arrow-down
                    1
                    ·
                    1 year ago

                    No they were not setting standards. They were in fact breaking them. Their own standards were not disclosed, forcing competitors to actually have to reverse engineer them in order to try to have a chance at compatibility. The whole reason for the lack of uniformity was Microsoft fucking with the standards!

                    Secondly, the competitors did not have a significant market share. Thirdly, it’s funny that you mention in the context of a developer, given that they all complain mightily, even to this day, about having to support the festering pile of IE versions still around. Still, this won’t stop you telling, so you go do your thing elsewhere please.

    • MagicShel@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      As recently as 6 or 7 years ago I maintained some apps that forced 5.5 compatibility mode. Because they were poorly architected in a shitty framework and no one was willing to do or pay for or train for a rewritten version. They were finally migrating to .NET when I left. It was the govt so they are likely wrapping up that migration now.