Microsoft considers adopting WebKit for Internet Explorer
appleinsider.com
Microsoft considers adopting WebKit for Internet Explorer
1–10 of 36 posts
Re: Microsoft considers adopting WebKit for Internet Explorer
#2Yes please.
Though this was apparently an off the cuff remark. I'll believe it when I see it. I also take anything reported by AppleInsider with a grain of salt.
Re: Microsoft considers adopting WebKit for Internet Explorer
#3God, I wish it was a possibility. But this headline seems specious. Ballmer's saying that for the time being Microsoft is staying the same. Them "considering" the route means nothing for current development.
If Internet Explorer become a WebKit browser I'd cry with joy.
Re: Microsoft considers adopting WebKit for Internet Explorer
#4What are the advantages for Microsoft if they were to make the change to WebKit? I know developers would love it, but is it really worth giving up complete control on their end? When it comes down to it they have their own best interest in mind, not developers'.
Re: Microsoft considers adopting WebKit for Internet Explorer
#5I don't really care much about their desktop browser, but dear God I hope they do something about the mobile one. It's truly awful.
I actually like WinMo 6 for the most part, but find myself using third-party browsers, which is not nearly as seamless an experience as it is on the desktop.
Re: Microsoft considers adopting WebKit for Internet Explorer
#6What are the advantages for Microsoft if they were to make the change to WebKit? I know developers would love it, but is it really worth giving up complete control on their end? When it comes down to it they have their own best interest in mind, not developers'.
They would have a faster and more compliant engine than they seem to be able to build themselves.
And "giving up complete control"? We're only talking about the rendering engine, not the rest of the browser. And WebKit is open source, they can just fork it if MS is unhappy with where it is going.
Re: Microsoft considers adopting WebKit for Internet Explorer
#7What are the advantages for Microsoft if they were to make the change to WebKit? I know developers would love it, but is it really worth giving up complete control on their end? When it comes down to it they have their own best interest in mind, not developers'.
They would have a faster and more compliant engine than they seem to be able to build themselves. And "giving up complete control"? We're only talking about the rendering engine, not the rest of the browser. And WebKit is open source, they can just fork it if MS is unhappy with where it is going.
> They would have a faster and more compliant engine than they seem to be able to build themselves.
I don't believe it's a lack of ability - Microsoft could easily produce a standard complaint browser. Adopting WebKit doesn't necessarily they would keep it compliant.
Given how important IE is to the Operating System in general, I doubt Microsoft could do this technically - not without breaking a raft of things... Given the incompatibility bumps with Vista I'll suspect they're would be seeking a more conservative path for the moment.
Re: Microsoft considers adopting WebKit for Internet Explorer
#8What are the advantages for Microsoft if they were to make the change to WebKit? I know developers would love it, but is it really worth giving up complete control on their end? When it comes down to it they have their own best interest in mind, not developers'.
They would have a faster and more compliant engine than they seem to be able to build themselves. And "giving up complete control"? We're only talking about the rendering engine, not the rest of the browser. And WebKit is open source, they can just fork it if MS is unhappy with where it is going.
So multiple incompatible branches of IE and then multiple incompatible branches of WebKit? Mozilla 5.0 (Internet Explorer; Microsoft; webkIEt (like WebKit (like gecko))). No thanks.
Re: Microsoft considers adopting WebKit for Internet Explorer
#9Earlier quoted context omitted.
They would have a faster and more compliant engine than they seem to be able to build themselves. And "giving up complete control"? We're only talking about the rendering engine, not the rest of the browser. And WebKit is open source, they can just fork it if MS is unhappy with where it is going.
So multiple incompatible branches of IE and then multiple incompatible branches of WebKit? Mozilla 5.0 (Internet Explorer; Microsoft; webkIEt (like WebKit (like gecko))). No thanks.
Multiple incompatible branches of WebKit is still better than the current situation.
Re: Microsoft considers adopting WebKit for Internet Explorer
#10Earlier quoted context omitted.
They would have a faster and more compliant engine than they seem to be able to build themselves. And "giving up complete control"? We're only talking about the rendering engine, not the rest of the browser. And WebKit is open source, they can just fork it if MS is unhappy with where it is going.
> They would have a faster and more compliant engine than they seem to be able to build themselves. I don't believe it's a lack of ability - Microsoft could easily produce a standard complaint browser. Adopting WebKit doesn't necessarily they would keep it compliant. Given how important IE is to the Operating System in general, I doubt Microsoft could do this technically - not without breaking a raft of things... Giv…
"Microsoft could easily produce a standard complaint browser"
So why don't they? Is it to hold back the web so that they milk their desktop applications like Office a little bit more?