> A fast moving standard is not necessarily a bad thing, provided that changes don't break backwards compatibility. Another problem is that the standard become

> A fast moving standard is not necessarily a bad thing, provided that changes don't break backwards compatibility. Another problem is that the standard becomes irrelevant. This is a concern for HTML5, because a 'rapidly evolving' standard means that things can be added prematurely - but once something is in the standard, it can't be removed (easily). At some point, you run the risk of having more companies go the Microsoft route and just abandon the standard altogether, and either stick with an older version, or just fork it into their own new language.