8 ms·
I'm sorry, but any guide that suggests you start by reading the entire specs for HTML, CSS and JS is just not realistic. The guide gets it right in the "practi
by untog 6y ago
I'm sorry, but any guide that suggests you start by reading the entire specs for HTML, CSS and JS is just not realistic.
The guide gets it right in the "practise" part, though: the beauty of the web is that you can write an HTML file and immediately see what you created in the browser. You don't need to read the HTML spec's instructions on Microdata before you do that.
- jiofih 6y agoThis is not a beginner’s guide, and the author acknowledged he himself has not read the full spec - it’s merely encouraged as a reference to go back to.
- detaro 6y agoI feel like for mastery the recommendation to read specs is a valid one. Not necessarily in their entirety, but they're worth exploring. And the HTML/CSS standards also often are useful as references.
- theandrewbailey 6y agoAgreed. In my experience, I've learned more from reading MDN than specs.
- jrochkind1 6y agoFew people have probably read those specs cover-to-cover with full attention. But never opening them is a mistake. The value of taking a look, skimming around, reading a few parts that seem interesting to you, is HUGE compared to never even having looked in there. And then continuing to do so when a curiosity arises.
- rimliu 6y agoIt is very realistic. The first thing I did when I got interested in HTML was to print out the spec. I do not get this attitude that blindly poking around for hours in hope to stumble upon something that works is superior to reading the docs.