-
code-review-000 | HTML5 Basics | Lessons
8-
Lecture1.1
-
Lecture1.2
-
Lecture1.3
-
Lecture1.4
-
Lecture1.5
-
Lecture1.6
-
Lecture1.7
-
Lecture1.8
-
HTML5 Basics – Philosophy of HTML5 (Part2)
Revolutions sometimes change the world to the better. Most often, however, it is better to evolve an existing design rather than throwing it away. This way, authors don’t have to learn new models and content will live longer. Specifically, this means that one should prefer to design features so that old content can take advantage of new features without having to make unrelated changes. And implementations should be able to add new features to existing code, rather than having to develop whole separate modes.
Things You Should Know
- HTML 5 was the first version of HTML to have a formal brand
- HTML 5 is intended to be the last numbered version of HTML
- HTML 5 has a primary goal to remain backward compatible (previous versions of HTML will work)
- Priority of Constituencies
- In case of conflict, consider users over authors over implementors over specifiers over theoretical purity. In other words costs or difficulties to the user should be given more weight than costs to authors; which in turn should be given more weight than costs to implementors; which should be given more weight than costs to authors of the spec itself, which should be given more weight than those proposing changes for theoretical reasons alone. Of coursea collection of information from which one learns, it is preferred to make things better for multiple constituencies at once.