Slashdot Mirror


Should Microsoft Switch To WebKit?

DeviceGuru writes "Although IE remains the one of the top browsers on desktops, it's being trounced on tablets and smartphones by browsers based on WebKit, including Safari, the Android Browser, and Google Chrome. Faced with this uphill battle on handheld mobile devices, Microsoft MVP Bill Reiss has suggested that it might be time for Microsoft to throw in the towel on Trident and switch to WebKit (though Reiss later decided he was wrong). But although there are lots of points in favor of doing so, there are also some good reasons not to, including security and a need for healthy competition to avoid having mobile developers begin to target WebKit rather than standards."

11 of 244 comments (clear)

  1. It's a silly proposition by Stormwatch · · Score: 4, Insightful

    IE's problem is not the engine, it's the shitty interface.

    (Ditto about Windows 8, many would say.)

    1. Re:It's a silly proposition by Runaway1956 · · Score: 5, Insightful

      AC says you're dumb - I disagree with him. Your opinion is pretty well thought out.

      I do, however, disagree with your assessment somewhat. Trident needs to die, and die hard. Microsoft needs to pull that abomination out of Windows completely, along with all the ActiveX controls, all it's privileges, all of it's quirks, both good and bad.

      I don't believe that I'll ever think that Windows is a "good" operating system, but the removal of Trident would make it one hell of a lot better. Sure, I know that many of IE's worst vulnerabilities have been "fixed", but I shall never forget how many vulnerabilities there have been, or how bad they have been.

      As for Webkit - I've liked it since it's debut under Google's name. Sure, I realize it's not Google's invention, but webkit is cool.

      If/when Microsoft shifts to Webkit, they really, really, REALLY need to install it as an unprivileged application, and make certain that it just BROWSES. It doesn't need hooks into dozens of programs, it doesn't need privileges, it doesn't need much of anything. A few plugins, addons such as Mozilla and Google offer for their own browsers. Leave it at that.

      A browser on Windows should be just as much, and no more than a browser on any Unix-like. The browser shouldn't even be used for updates, as Microsoft has done for all these years. A separate and distinct updating program is a requirement, with no overlap in privileges.

      Yes, Trident needs to die, quickly, and hard. It would be a wonderful thing if five years from now, Trident were just history, with zero support anywhere. I'd like to see websites assist people with updating from Trident simply. Just stop coding for Trident.

      "This site is best viewed with ANY browser that is not Internet Explorer!"

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    2. Re:It's a silly proposition by Billly+Gates · · Score: 4, Insightful

      Trident in IE 10 scores a decent in HTML 5/5.1 and CSS 3.

      It is not the piece of crap it once was in IE 6. Just because you have not used it in 12 years doesn't mean it is the same as in 2001.

    3. Re:It's a silly proposition by Nerdfest · · Score: 4, Insightful

      The problem is that if they start getting a significant share of the browser market again, they're almost guaranteed to start their old extend/extinguish trick. Microsoft needs to stay an 'also ran' in the browser market until they learn to play with others.

  2. Arguments of convenience by blarkon · · Score: 5, Insightful

    In the past many on Slashdot argued vehemently for web standards. It's interesting that a lot of people who used to be pro-web-standard when Microsoft was non-compliant with IE are now saying "hey, we're only going to target webkit because ..." The same reasons that applied to avoiding an IE monoculture for web development apply to a webkit monoculture. Rather than bathing in schadenfreude, people should be kicking over bins just like they did with IE to ensure that the most popular implementation follows the standard, not the standard follows the most common implementation.

    1. Re:Arguments of convenience by ikaruga · · Score: 4, Insightful

      Arguing against IE back in the days made sense because it was a closed-source engine controlled by one company with monopolistic policies. Webkit is open source, anyone can implement it anywhere and anyhow they want. What else do you want? If you ask me, webkit could become the web standard itself, and as long as it's renewed every few years for new features(webkit2 is already in the works, btw), I wouldn't care. The only webkit related issue I can think of is the iOS gimped implementation, but that is more of an Apple problem than Webkit problem.

    2. Re:Arguments of convenience by Billly+Gates · · Score: 4, Insightful

      I do not give a shit whether it is opensource. I do give a shit whether it enslaves the web and enforces another decade of stagnationm, where we can't move on to HTML 6 and corps lock a special version of Chrome from this decade to support their apps.

      Maybe Android 3.x will be used and corps will downgrade their phones for just that one version 10 years from now if the W3C makes changes that the current webkit does not support. Only Google's way of doing it is different.

      IE 5.5 was cutting edge and MS was inventing new standards and it was the best browser back then. THe problems came when w3c decided to recommend the same standards implemented differently. Then IE 6 did things one way, and Firefox rendered them in another.

      Open source or not I do not want to see that problem again.

  3. No, they simply should adhere to the standards. by Xiph1980 · · Score: 5, Insightful

    Why should Microsoft move to WebKit? I mean, yeah, it's a more secure browser engine perhaps, but it's still their prerogative to use their own. I think it'll be more important for Microsoft -- and any browser (engine) for that matter -- to follow the W3C standard accurately, possibly with their own extensions if they want, but in the basis they should support the standard to make sure web sites render uniformly and accurately over all browsers.
    That'll finally bring more choice to the user, in stead of the pseudo-choice now.
    I prefer opera and have that installed as my default browser, but still have IE and Chrome installed because some websites will only work on either of those. Between the three I can open all sites that I need, but it shouldn't be necessary if all just follow the standards, and consequently, all web sites only need to be written to that standard as well.

    --
    Manuals are your last resort only
  4. No, and I love Webkit. by Anonymous Coward · · Score: 4, Insightful

    Trident is getting better with each major release, which is a good thing.

    And Microsoft still has some input towards standards as well, such as the WebRTC spec if I remember correct, or something similar that also had some features missing from it.

    Yeah, you could argue that things would be simpler if there was just ONE thing, the one thing that correctly interprets the specs, but it is also those incorrect spec implementations that have driven competition, driven the creation of new ideas to replace old ones and inspired so many developers to create methods to deal with them in their own ways.
    Not only that, without all this mess, there would be no experimentation with future specs, and all these separate browsers lead to browser prefixes being implemented, even by Microsoft recently.

    The main problem with web dev is most devs are terrible. Admittedly that is mainly a problem with such inconsistency in JavaScript, and HTML allowing spaghetti syntax all over the place.
    And lets not get started on scope. Holy crap, so many people are clueless about it. And again, that it is true globally in any form of programming. Abuse of global namespaces being the biggest headache in all programming, such things that make you want to headbutt your monitor with your fist, a physical impossibility! But damn it I will find a way and collapse the universe just so THEY don't exist!

    The next huge change in JS is going to bring a lot of new features, but also a bunch of changes to the way JS is executed.
    It is going to be a shaky decade when that comes about. But it will be for the better. I hope...

  5. Konqueror indeed! by Dr.+Spork · · Score: 4, Insightful

    I wonder if the people who were writing KDE back in the 90's ever suspected that their code would make it so far! If they heard 15 years ago that some Microsoft MVP would be talking about replacing the rendering engine of IE with the rendering engine from Konqueror, they would have shit themselves.

  6. Re:Ditch HTML5 for stronger web and user protectio by Billly+Gates · · Score: 4, Insightful

    Webkit is making MS honest.

    Have you tried IE 10? I know the thought probably sends shiver down your spine but I have to say MS really is caring and shaking in their boots. It is a great browser. I fear webkit becoming too dominate at this point and Windows Phone users are whinning they can't view mobile sites as they cater to just webkit.

    I can't advocate openstandards and bash IE 6, yet fully support webkit at the same time. I would be a hypocrite otherwise. What if you want to use FirefoxOS in your next phone? Will you be screwed over? Right now, yes.

    IE has standard behavior now. Since IE 9 it passed all the acid tests. Just because you hate one browser doesn't mean you should support the entrenchment of another or support things like html5test that test non standard non implemented things. It encourages all the things that caused IE to be proprietary when implementations of things like the CSS box model came about locking corporate desktops up for decades.