I guess it comes to a point where you decide what you want the project to be (and draw a line in the sand).
I could also (1) make it not hidden, and (2) make it enabled by default, but I don't know to which extent people are interested in keeping support for OSes that haven't been patched for security in at least 8 years (for Windows 2000), more for the others...
Cutting Edge and Nimble or Encumbered by hacks for old browsers.
For a hack to make it into Wedge, it has:
- To mean that I actually use the browser in my test suite. I dropped IE6 from said suite last week, so it will no longer be getting new hacks. I still have IE7 in my suite, but I really don't care about it. Its market share is even less than IE6's...
- Not to be cumbersome to other browsers. That is, if a hack forces me to make a chance for other browsers, or if it adds bytes for all browsers (which it never will, thanks to Wess!), then it's a no-go for me.
I can definitely understand that, although I am the opposite, I usually end up reinstalling my OS every 6 - 12 because I either break it or get the shits with it's performance.
Basically, I use Classic Shell, it does 95% of the job. :P