61–67 of 67 posts
Earlier quoted context omitted.
It was, though it was also designed with Embrace, Extend, Extinguish in mind. ActiveX anybody?
NaCl anybody?
Yeah, the detractors of IE are just mindlessly posting "IE SUCKS" over and over for no reason. It's not that the browser is seriously lacking, or that it's been behind for so long and actively blocking open standards. It's that the internet is dumb and people just love to hate.
To be fair for every web developer with legit gripes about IE there probably are about 100 people posting "IE SUXX" on youtube. Most discussion of technology on the internet is just noise written by people who don't have the slightest clue what they are talking about.
Earlier quoted context omitted.
> At least give Microsoft credit: IE10 is a modern, standards-compliant browser. For how long? Hell, we know microsoft will have to be pushed kicking and screaming into supporting WebGL (and likely the fullscreen API as well as they go hand-in-hand), and they've just proposed their alternative to WebRTC (how not unexpected). See also: their proposing a brand new touch API, but not implementing the one which everybody…
> supporting WebGL I think it's reasonable they might implement it on top of DirectX and then tell us how much faster it is. > likely the fullscreen API as well as they go hand-in-hand Why does Metro IE need the fullscreen API? Pointer lock maybe, but what's the use of going fullscreen in a fullscreen browser?
I'm not aware of their even planning to do it.
> Why does Metro IE need the fullscreen API?
1. IE is also available in desktop mode
2. The fullscreen API allows making a given element of the page, such as a video or a canvas, fullscreen. Not just remove the browser chrome
3. Even if the API was a noop in a chromeless browser — which it is not — it can be implemented as a noop for compatibility
4. Fullscreen web application may benefit from disabling e.g. some of the built-in gestures where that makes sense
For me, IE is like landmines. Built as weapon to break the web rather than to do anything constructive, and then abandoned after the war to create more havoc for years. Maybe MS should have given the new generations of IE a new name. Rebranding would probably have been cheaper and more effective than marketing campaigns trying to make IE respectable.
Earlier quoted context omitted.
> supporting WebGL I think it's reasonable they might implement it on top of DirectX and then tell us how much faster it is. > likely the fullscreen API as well as they go hand-in-hand Why does Metro IE need the fullscreen API? Pointer lock maybe, but what's the use of going fullscreen in a fullscreen browser?
> I think it's reasonable they might implement it on top of DirectX and then tell us how much faster it is. I'm not aware of their even planning to do it. > Why does Metro IE need the fullscreen API? 1. IE is also available in desktop mode 2. The fullscreen API allows making a given element of the page, such as a video or a canvas, fullscreen. Not just remove the browser chrome 3. Even if the API was a noop in a chro…
This ad isn't about the merits of IE as a browser, this ad is about building a preformed thought in the common users mind whenever they hear someone bash IE. IE hasn't been the victim of bad PR, it has earned it's reputation through years of blood/sweat/tears by the hands of developers. Microsoft recognizes that they won't be able to change this attitude in the developer community, but that they can lessen the weight…
With all 300 views...I doubt it will change anything at all. (EDIT: MY opinion will say the same until that view counter says a million and I highly doubt it will even get close. The only people who really care anyway are the "trolls" that Microsoft is talking about!)