CSS frameworks, boilerplates and reset.css could probably be condensed into a single point. (HTML5 boilerplate already contains some form of reset.css anyway)
I guess some people just like to write their frontend code from scratch...? It's funny because the author wrote Zepto, of all people he should know about abstracting away cross-browser concerns.
Right? Man I feel like I'm missing something huge here if somehow reset.css and HTML5 Boilerplate are creating technical debt for me. I think I've launched at least 10 projects using it and I've never once had to say "oh that's a weird thing that HTML5 boilerplate does, here's how you compensate for it" like you have to do with Bootstrap or Foundation or things that DO create debt.
I think the point was that they weren't completely necessary, and it would create a dependency on their continued use? I'm not sure, but that's what I got, and I don't agree. NOT using CSS frameworks creates a pretty radical dependency on NOT using them in your design going forward. Sometimes the costs of not doing or using something create a lasting debt.
There's an alarming stench of NIH in some of the authors points, co-mingled with some more salient points about not over-engineering up front.
I guess some people just like to write their frontend code from scratch...? It's funny because the author wrote Zepto, of all people he should know about abstracting away cross-browser concerns.