I know this post is a bit late, but perhaps it will help for future
pushes.
The main reason that IE is still the primary browser is because
Microsoft tackles this issue on one primary front, the developers.
It may cost a lot sometimes, but Microsoft makes it really easy to
write code and applications that only work well on IE. It simplifies
concepts like web services, and ajax and makes it really easy to use
activeX controls which do not work in any other browser (I'm not sure
any other browser legally can support those). Some web technologies
like SharePoint only work well with ActiveX controls and now that
SharePoint makes it so simple for the lay person to create web
content, I think we will be seeing many more sites out there that will
work on other browsers, but simply can't work as well on those
browsers as they do on IE. Indeed, even though I prefer Firefox, I
have to have IE for those, just in case, times when FF wont work.
Sometimes I think it would be easier to just use IE all the time. IE
tab, helps, but that brings up another point for me. Every time a new
version of FF comes out, I find myself having to wait until all my
addons get upgraded, and if the original developer has stopped
maintaining it, sometimes I end up losing a good addon, permanently.
Anyway, it would be helpful if there were some sort of tool suite out
there that did a good job of competing with the Microsoft tools that
is 1. Easy to learn and 2. Well supported and 3. Has a license
structure that would require minimal legal work for businesses to
protect their own privacy and financial interests. 4. Does a good job
of supporting multiple languages like VB, C#, Ruby, Pearl, Python, and
maybe even some flavors of older languages like Pascal, COBOL and
Fortran, 5. Supports things like AJAX, Accessibility, XML, XSL and
easy data access 6. Ties this all in with things like Bugzilla,
Subversion, Unit/Regression testing tools and a good debugger and 7.
Simplifies security issues pertaining to the Web and PCI DSS
standards. Please note, the learning curve for this should be
relatively low, too.
VSTS already does much of this (but costs and arm or two and a leg). I
would personally like a suite that does a better job of supporting non-
proprietary standards and best-practices.
If there were a tool set out there like I described that could compete
with VS, then I think it would not be long before a lot of web sites
were more favorable to FF and other browsers, simply because those
browsers actually do work better than IE and it is only the
proprietary code that makes it seem otherwise.
Later