Quote:
|
Originally Posted by fryke Then again, there's a fine line between things. Often. For example: Standards are good. They enable a common ground. But without moving off of old paths, there's no evolution. And why leave all evolution to standards organisations. So you develop something new. It's good. You want to push it towards a standard. It doesn't get accepted. Now what? Kill the product or let it live and thrive? |
This is a good point if I am interpreting it correctly.
Look at JavaScript for example. IE has a lot of functions/objects that no other browsers support, and it has set some standards that other web browsers have adopted, XMLHttpRequest for example.
A lot of the problems we non IE people have with JavaScript sites we can't blame on Microsoft, because most of their JavaScript implemention follows web standards, they just have some extra functions they thought would be cool that they put into their browser. We really have to blame the web designers that used those features for our issues. A lot of times there are ways to do the same thing that just take a little more work with standard code.
Now once we get into css thing, I don't see a whole lot of innovation on MS's part there, they just missed the mark, worse than most browsers. Not a whole lot of browsers complete the Acid2 test succesfully, including Firefox which just moved to v1.5. That said Firefox is a lot closer than IE.