Microsoft’s surprise decision to work with Google on its Edge browser
1–8 of 8 posts
Re: Microsoft’s surprise decision to work with Google on its Edge browser
#2I'm surprised by this.
Why can Google afford to keep up but not Microsoft?
Do you think the fact that Safari is lagging behind Chrome and Firefox also means Apple does not want to invest as many resources as Google?
Re: Microsoft’s surprise decision to work with Google on its Edge browser
#3> The web has been moving at a far more rapid pace in recent years, with Google pushing a lot of new standards and speed with Chrome, and Microsoft didn’t have the structure to keep up. I'm surprised by this. Why can Google afford to keep up but not Microsoft? Do you think the fact that Safari is lagging behind Chrome and Firefox also means Apple does not want to invest as many resources as Google?
I think this is a smart move by Microsoft. By doing less and building on what already exists, you can concentrate your resources. Much like coming up with Typescript rather than trying to replace JavaScript.
Re: Microsoft’s surprise decision to work with Google on its Edge browser
#4Re: Microsoft’s surprise decision to work with Google on its Edge browser
#5It would be nice to see Apple jump in as well, so we'd have a common rendering platform. In my mind, we all have the same network stack (TCP/IP + HTTP + SSL), so why not have this layer too.
Microsoft is proving that you can have a lot of standardization, but still get a custom implementation without having to bet the farm.
Re: Microsoft’s surprise decision to work with Google on its Edge browser
#6Re: Microsoft’s surprise decision to work with Google on its Edge browser
#7This has an interesting side-effect: Apple is now left out on it's own with a webkit-based browser. (Yes, I'm ignoring Mozilla at the moment.) It would be nice to see Apple jump in as well, so we'd have a common rendering platform. In my mind, we all have the same network stack (TCP/IP + HTTP + SSL), so why not have this layer too. Microsoft is proving that you can have a lot of standardization, but still get a custo…
Re: Microsoft’s surprise decision to work with Google on its Edge browser
#8This has an interesting side-effect: Apple is now left out on it's own with a webkit-based browser. (Yes, I'm ignoring Mozilla at the moment.) It would be nice to see Apple jump in as well, so we'd have a common rendering platform. In my mind, we all have the same network stack (TCP/IP + HTTP + SSL), so why not have this layer too. Microsoft is proving that you can have a lot of standardization, but still get a custo…
You are confusing standards with implementations.
But if you look at SSL, at one time there was a bunch of overlap of people using OpenSSL libraries. I was trying to compare to that.