Rapid Browser Development Challenges Web Developers 221
Esther Schindler writes "Feeling a little overwhelmed by changing web standards and new browser choices? You aren't the only one. Mozilla is launching development tracks for the next two editions of its Firefox Web browser immediately, with hopes to push both into general release before the end of the year. This while Microsoft previews Internet Explorer 10 on the heels of its IE9 release, and Google projects Chrome 13 just one year after Chrome 7. Meanwhile, HTML5, the next version of the Web's primary language, appears to have entered a permanent gestation phase. Writes Scott Fulton: All the confusion has prompted Web developers to ask this question: What do we develop our sites against now?"
HTML 3.2 (Score:4, Funny)
HTML 3.2. If you can't do it with HTML 3.2, you don't really need to do it.
Re:HTML 3.2 (Score:4, Funny)
Re:Hit standards, miss the market (Score:5, Funny)
See comment on "testing" - if we simply targeted standards, we'd never deliver product.
You target standards, and test with a validator before it even hits the first browser in test phase 2. That reduces the delivery time.
Especially when a new browser comes out in the middle of the development process, and you won't have to rewrite a single line of code.
Oh, and it will be future proof too, and work just as well in Firefox 7 as in IE 12.
Re:Flash (Score:1, Funny)
Re:why, standards, of course (Score:3, Funny)
protect you against allot of Virus & Malware treats.
Mmmmm tasty Malware Treats. Get yours now!