3 ms·
> Microsoft seem to keep their habit of adding proprietary prefixes and stuff, but on the other hand, so does webkit and firefox too. Let me just say it sucks.
by mryall 15y ago
> Microsoft seem to keep their habit of adding proprietary prefixes and stuff, but on the other hand, so does webkit and firefox too. Let me just say it sucks.
This is actually recommended practice for vendors supporting CSS properties which aren't yet standardised or passing testing against the relevant standard.
It is supposed to help prevent the situation where one vendor's implementation of a property becomes the de facto standard simply because it is the first one implemented.
> At the moment it still looks pretty lame I'd say.
They only released IE9 one month ago. What are you comparing it to? Is there some other browser development team that has achieved more in a single month of development?
I think it's great that Microsoft continues to be open and put their previews out frequently for testing and feedback. Rather than throw meaningless words around like "lame" and "sucks", how about some suggestions on what they should do differently?
- robin_reala 15y agoIt’s not really one month of development. This would have been 6 months of development by two thirds of the team while the rest worked on IE9 polish bugs.
- BasDirks 15y agoIE just plain sucks, and they're lagging behind much and often. Suggestions about what they should do differently? Kill the whole IE project and make Chrome/FF default?
- hellweaver666 15y agoI don't care about the browser, what I want to see is them adopt one of the modern rendering engines - preferably webkit as that team seem to be doing an awesome job of staying ahead of the curve.
- karl_nerd 15y agoGood point about vendor prefixes. The problem is that once implemented, it takes very long time for them to go away. I thought i wrote what i wanted in the headline. I want to see or hear about webGL and websockets. I'm quite sure others are disappointed because of the lack of CSS transitions. Maybe they should've waited a while before releasing if they couldn't implement more CSS3 features.