The Back(side) of the Class
summary
Claims that class-based methodologies solve performance, coupling and maintenance get tested: expert numbers show problems appear only at 20,000 DOM elements not typical sites, and most pages have 900 DOM elements and about 50 complex selectors. Practical examples show classes pushing styling into HTML, forcing repeated edits rather than single-rule refactors. Tooling and preprocessors like Sass Grunt Autoprefixer Susy create dependency bloat. Concrete guidance favors using the cascade and inheritance, selective refactoring, clear documentation and starting simply rather than one-size-fits-all rules.
AI-written summary · about
chapters (46)
- 0:00Intro
- 2:55Dont be offended
- 3:27Why so many frameworks
- 4:03The spirit of sharing
- 5:10PPK bombs
- 6:00Performance claims
- 6:31Steve Souders
- 8:09Less Refactoring
- 9:24Possible Problems
- 9:42CSS as a Programming Language
- 10:19Dont Try to Make it into a Programming Language
- 10:57Square Peg
- 11:32Side Effects
- 13:43Project Overview
- 14:30Module Modularization
- 15:07Efficiency
- 16:03Tools
- 17:47Frameworks
- 17:58Dependencies
- 19:38Largescale complex
- 20:27BEM
- 21:30Problem Solving
- 22:39Inheritance
- 23:44Embrace the Chaos
- 26:50Start Simply
- 27:59Respect the Content
- 32:17Bitter Gunner
- 33:05axiomatic CSS
- 34:27Refactoring
- 35:07Documentation
- 35:52BEM Documentation
- 36:13Table of Contents
- 37:00Dont teach people how to write CSS
- 37:26Keep things simple
- 37:53Health provider website
- 39:06Being principled
- 40:05Sean Diddy Combs
- 40:55Its not simple
- 41:44Its not good enough
- 42:29Changing people
- 43:10Harmful
- 43:41Job Market
- 44:45Conformity
- 45:16Containers
- 45:45Cleaning up the Internet
- 46:48refactoring is not a bad thing
