Slashdot Mirror


Former Edge Browser Intern Alleges Google Sabotaged Microsoft's Browser (ycombinator.com)

Joshua Bakita, a former software engineering intern on the Edge team at Microsoft, says one of the reasons why Microsoft had to ditch EdgeHTML rendering engine in Edge browser and switch to Chromium was to keep up with the changes (some of which were notorious) that Google pushed to its sites. These changes were designed to ensure that Edge and other browsers could not properly run Google's sites, he alleged. Responding to a comment, he wrote: "For example, they may start integrating technologies for which they have exclusive, or at least 'special' access. Can you imagine if all of a sudden Google apps start performing better than anyone else's?" This is already happening. I very recently worked on the Edge team, and one of the reasons we decided to end EdgeHTML was because Google kept making changes to its sites that broke other browsers, and we couldn't keep up.

For example, they recently added a hidden empty div over YouTube videos that causes our hardware acceleration fast-path to bail (should now be fixed in Win10 Oct update). Prior to that, our fairly state-of-the-art video acceleration put us well ahead of Chrome on video playback time on battery, but almost the instant they broke things on YouTube, they started advertising Chrome's dominance over Edge on video-watching battery life. What makes it so sad, is that their claimed dominance was not due to ingenious optimization work by Chrome, but due to a failure of YouTube. On the whole, they only made the web slower.

Now while I'm not sure I'm convinced that YouTube was changed intentionally to slow Edge, many of my co-workers are quite convinced -- and they're the ones who looked into it personally. To add to this all, when we asked, YouTube turned down our request to remove the hidden empty div and did not elaborate further. And this is only one case.

13 of 427 comments (clear)

  1. Yes, we can imagine by NaCh0 · · Score: 5, Insightful

    Can you imagine if all of a sudden ________ apps start performing better than anyone else's?

    Yes we can. Ask the DR-DOS team.

    1. Re:Yes, we can imagine by Anonymous Coward · · Score: 5, Insightful

      Attitudes like this are basically the reason people are going to pissed in about 10 more years when Google really is the new Microsoft. We have the chance to fix the issue now, but people like you are too obsessed with rubbing Microsoft's nose in the dirt over 15+ year old mistakes to realize you're enabling Google to do the exact same shit.

    2. Re:Yes, we can imagine by Anonymous Coward · · Score: 5, Informative

      Except that's not what actually happened.

      When Windows 3.1 was in Beta, Microsoft put in some code that displayed an error message if you weren't running Microsoft's own MS-DOS. But all it did was display an error message. You could just ignore it and Win 3.1 would still run -- I was running DR-DOS at the time and it worked just fine.

      A few beta testers were using DR-DOS and word got out that Microsoft had done something to prevent people from using anything other than MS-DOS. In the official retail release of Win 3.1 Microsoft changed the code and deactivated the error message. It was still in there but didn't display. You could activate it by using a hex editor to change a couple of bytes.

  2. Re:Boo hoo by jellomizer · · Score: 5, Insightful

    Microsoft has to learn how to make software like everyone else. You need to keep compatibility with the big fish, and not just do your own thing, and thinking everyone will switch to your method.

    I am sorry, I had to code too many IE 6 workarounds and not put in new features due to having to keep IE 6 compatibility for so long, I have no sympathy to this Edge engineer.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  3. Re:Boo hoo by DontBeAMoran · · Score: 5, Insightful

    The enemy of your enemy is not necessarily your ally.

    --
    #DeleteFacebook
  4. Re:Embrace Extend Extinguish by 93+Escort+Wagon · · Score: 5, Insightful

    We may be seeing Microsoft getting a taste of its own medicine.

    So is it really okay if Google screws over other web browsers with Chrome-specific hacks, just because Microsoft did it a decade or so ago? Cuz in doing so, Google is also causing problems for people who aren't using Edge or Internet Explorer.

    I think if it was evil when Microsoft did it, it's also evil if Google does it.

    --
    #DeleteChrome
  5. Re:Embrace Extend Extinguish by markdavis · · Score: 5, Insightful

    >"Satisfying as that may be, it still change Google into a bunch of hymn singing angels."

    Exactly. Which is why it is more important than ever to support Mozilla Firefox. We absolutely do NOT want to end up with Google in control of everything.... any more than what we dealt with when Microsoft was ruining the web.

    There was a time when Chrome pulled ahead of Firefox in performance. That time ended. It is a good time to switch to or switch back to Firefox. You will have web-standards-based browsing on all platforms, open source, open development team, just as many addons, but with more user control and customization.

  6. Re:Embrace Extend Extinguish by Pentium100 · · Score: 5, Interesting

    No, but it's like seeing the previous dictator swinging on a rope, put there by the new dictator who is exactly the same. The state of the things didn't change, but the good feeling of "an asshole getting what was coming to them" is still there.

  7. Microsoft "Teams" sabotages Chrome by ffkom · · Score: 5, Informative

    BTW: The web version of Microsoft "Teams" runs fine with Chrome on Linux, but only if the "UserAgent" is faked to indicate a Windows-based browser. Exactly the same evil strategy, used as of today, by Microsoft.

  8. Re:Boo hoo by markdavis · · Score: 5, Insightful

    >"But it's not so funny when (or if) Google adds stuff that slows down Firefox or other open source competitors to Chrome."

    Bingo. And if anyone thinks that isn't already happening or won't happen, they need a reality check. Chrome has decimated Firefox's market share- and most of it undeserved. Firefox is the last light in the "true" open-source, multi-platform, modern browser era. We will all absolutely be worse off if that light is extinguished.

    Ask yourselves if there is really any good reason now to "automatically" install Chrome on machines or recommend it to friends and family. If not, consider making it Firefox. The painful redesign of the Firefox engine that lost some of the addons ended up making Firefox just as fast and more resource friendly while still being much more user-oriented and configurable than Chrome... and with a huge bonus of not being tied into all kinds of other incentives to do bad things with your data. (Looking at you, YouTube/Android/Gmail/Gmaps/Gwhatever users..).

  9. Re: Boo hoo by ironicsky · · Score: 5, Insightful

    I came here to say this.

    ActiveX
    Silverlight

    Incompatible CSS and IE specific JavaScript.

    Microsoft is one of the reasons the internet was a standards nightmare, while Mozilla, Google and Opera all played nice with standards, Microsoft didn't.

  10. Re:I Believe It by alexo · · Score: 5, Interesting

    I use FireFox, both mobile and desktop, and google docs and spreadsheets work fine for me. Haven't tried Slides recently but it worked fine the last time I did.

    Open Google's image search in mobile Firefox.
    Then do it in mobile Chrome.
    See the difference in functionality?
    Now change Firefox's user agent to masquerade as Chrome.
    Suddenly the full functionality is back.

  11. Re:Boo hoo by Tuidjy · · Score: 5, Insightful

    Google would be able to change YouTube's code a lot faster than Microsoft could push out updates for Edge.

    And Microsoft is well aware of this. Why? Because that's exactly how they were conducting their "embrace, extend, extinguish" policy when they were the big bully on the block.

    Do you notice that it's an intern complaining, and not an official Microsoft statement? I guess that they are ashamed, or unwilling to remind those of us who remember of all the hoops we had to jump to keep stuff IE (was it 6) compliant. Client side VisualBasic, not-quite JavaScript, non-compliance to standards, etc.

    Google has read Microsoft's "Book of Evulz", and is following it to the letter.

    --
    No good deed goes unpunished...