61–70 of 774 posts
That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.
Also, Blink is only the renderer. Safari does not use V8.
Very sad. I'm not a Microsoft fan but I thought this was one of the things they were doing right. The performance was really good, compatibility with standards was actually the best IMHO. Every thing (SVG) I tried that got past Firefox and Chrome worked on Edge without modification. And yeah, we need the competition. It's not like Microsoft is running out of money. Guess they need their most talented people doing som…
Unfortunately it wasn't. See caniuse.com.
> And yeah, we need the competition.
This is the key point. Indeed. Google becoming the ultimate web monopolist seems scary. I just hope Mozilla is going to be able to keep competing (but I'm not sure how long will it stand, a neighbour post says "Firefox desktop market share now below 9%"). I wish MS could choose the Mozilla engine instead...
Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.
There are over 2 billion iOS devices and every browser on iOS—Firefox, Chrome, Brave—uses WebKit.
Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.
Interesting, but what I really, really want them to do is EOL IE 11 so that the web can move forward without feeling guilty about the X% of users still on it. IE 11 has unfortunately become the new IE 6. As it is right now I believe the IE 11 EOL is tied to the Windows 10 EOL...which is not happening anytime soon. Many frameworks are dropping support for it anyway so I guess it will end up being defacto desupported.
As someone who has (luckily) only had to support Firefox/Edge/Chrome, can you go into why IE11 is so bad? In the very small amount of testing I've done, everything seems to render just fine (especially compared to IE6/7/8)
Interesting, but what I really, really want them to do is EOL IE 11 so that the web can move forward without feeling guilty about the X% of users still on it. IE 11 has unfortunately become the new IE 6. As it is right now I believe the IE 11 EOL is tied to the Windows 10 EOL...which is not happening anytime soon. Many frameworks are dropping support for it anyway so I guess it will end up being defacto desupported.
As someone who has (luckily) only had to support Firefox/Edge/Chrome, can you go into why IE11 is so bad? In the very small amount of testing I've done, everything seems to render just fine (especially compared to IE6/7/8)
That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.
Interesting, but what I really, really want them to do is EOL IE 11 so that the web can move forward without feeling guilty about the X% of users still on it. IE 11 has unfortunately become the new IE 6. As it is right now I believe the IE 11 EOL is tied to the Windows 10 EOL...which is not happening anytime soon. Many frameworks are dropping support for it anyway so I guess it will end up being defacto desupported.
As someone who has (luckily) only had to support Firefox/Edge/Chrome, can you go into why IE11 is so bad? In the very small amount of testing I've done, everything seems to render just fine (especially compared to IE6/7/8)
The reason why IE11 will live for a long, long time is it's compatability modes. You can run apps all the way back to IE7 on it. And yes these still exist.