Some of the replies I agree with. Some of them I don’t. There was, however, one nugget I found particularly interesting.
Mike Loizides said (emphasis mine):
Would it be a leap too far to imagine that the W3C takes on the task of developing (and maintaining) a core rendering engine that the browser manufacturers can base their browsers on? Everyone gets given the same basic renderer which they can then bolt other stuff onto. So they get more time to come up with those all-important unique selling points that drive revenue.
Am I onto a winner or shall I get my coat?
I wonder: would it be a leap too far?
In my previous post on Andy Clarke’s call for the CSS Working group to treat specification development like any software company developing software does, I said:
The W3C participants who dream up CSS specs don’t deliver THE companion product that renders the CSS according to the plan. CSS is dependent upon an “outside” product — the web browser, manufactured by entities other than the W3C. Obviously, this complicates matters.
Is there hope for a vitamin k for cats
solution in "web code" specification development in having the W3C create and maintain a core web browser engine? Would it simplify things?
Maybe it would. It would be one step toward being able to treat spec development in the manner that Andy suggested. It might lighten the burden of Microsoft from figuring out how to meet standards without breaking the web. Their team can focus on bells, whistles and other technologies and get out of the line of fire coming from web developers/designers for a change.
Maybe this idea is completely unrealistic. I accept that it very well may be. It is interesting to consider anyway.