xav wrote:Without CSS there would be no View=>Page Style=>No Style menu option in Firefox - and I would have no real recourse when faced with a web page with some godawful combination of colours and fonts. Heck, it even works on pillarbox websites made that way by their style sheets.
That would be great if it worked. The problem is that style-sheet-based pages tend to end up in a terrible mess when you turn that off. Much worse than a generally un-styled page needs to be; to the point that it's generally better to put up with the cack-handed layout than try to go without.
I'm not convinced that there's enough consistency between sites that you can set up a preferred layout that's going to work with many of the sites you're interested in, so you end up hacking on each site one by one, by hand.
xav wrote:You claim that having IE development stagnate was good because it prevented the developers being distracted by flashy new features so they could concentrate on fixing the current issues. You then point to "going fast" as one of the current issues. But given that IE is considerably slower than its competitors, how exactly do you think that stagnation has helped to fix that issue? While the other, non-stagnant browsers have been working on new, faster rendering code and javascript engines, stagnant IE has only barely improved in speed.
Well, I wouldn't
advocate using IE. It's a bag of shit. The benefit it provides is that the faceless masses that I don't know or care about do use it, and they're the ones holding back the internet from an unrestrained spiral of eternal upgrades.
That lot (Windows users) are great. They also act as a massive array of honeypots by running especially insecure software which distracts internet evildoers from turning their attention to the harder-but-not-bulletproof platforms I'm more inclined to use.
xav wrote:Not every new feature necessarily implies bloat and slowdown. Some of the newer CSS effects are aimed at moving common tasks away from the slow and heavy Javascript+images approaches that are used today, towards implementation in the core of the browser - where they can be made fast and low-impact.
I'm not sure it makes much difference when the majority of your browser is written in javascript as well. Certainly the principle of a thick client providing a library of platform-specific optimisations to implement features in the most efficient way is good for speed in some sense -- but development practices have gone in the opposite direction, so you might as well stay with a thin client and focus on consistency.