The Geek Gathering Conference - recap

Transcript

2. Speakers DOUGLAS CROCKFORD HARRY ROBERTS ZOLTÁN NÉMETH MARTIN NAUMANN JEF CLAES ATTILA SZEGEDI ANDREW DAVEY RATKO ĆOSIĆ ANTON CACERES
3. What is CSS Framework HARRY ROBERTS
4. • https://speakerdeck.com/csswizardry/what-is-a-css- framework-anyway • #wtframework • History of frameworks: ◦ yui - 2005 ◦ blueprint 2007 ◦
5. Problem with frameworks • Far too bloated. • Most projects are unique—how can standard CSS • accommodate bespoke UIs? • Far too prescriptive and opinionated. • They try to be all things to all men. • They get in your way.
6. Bloat Size over the wire is bad for performance (i.e. users). Size on the filesystem is bad for developers
7. Unique projects This is the problem with (conf)using UI Toolkits. Fully designed components aren’t reusable cross-project.
8. Opinionated To an extent, they need to be… …but only in the right places.
9. They try to be all things to all men Responsive. Mobile-first. Flat design. 101 specific components. Sold as a ‘framework’.
10. Why so many? Opinionated developers. Subtle differences. Selfishness. Perception of inability
11. CSS frameworks vs. ‘others’ Everyone loves jQuery, Symfony, AngularJS, etc. Everyone hates CSS frameworks.
13. CSS Frameworks vs. UI Toolkits UI Toolkits are often miss-sold as CSS Frameworks.
14. UI Toolkit • A full-on product. • Implemented, not worked upon. • Does the majority of the work.
15. • Great if you need a full UI out of the box. • If you’re not great with either design or front- end dev. • Fantastic for prototyping. • Not suited to client work, or working with bespoke designs.
16. CSS Framework • A helping hand. • Should guide and lead decisions. • More of a concept than a product. • Makes up the minority of a project
17. • Good if you need help with scalability or architecture. • Good if you aren’t particularly good with CSS… • …but do have your own designs.
18. UI Toolkit Does the work for you. Quick-win. Answers the ‘what?’ Gets the job done. CSS Framework Offers a helping hand. Major commitment. Answers the ‘how?’ Gets the job started.
19. What’s wrong with CSS? It’s old. Really old. It can’t be changed. It operates in a global namespace. It’s based on inheritance. It’s very, very loose. Source order is critical. The cascade needs managing. Specificity negates all of the above
20. What CSS framework should be? An enabler. A helping hand. A school-of-thought. Highly configurable. Design-free. Ignorant/agnostic.
21. • Don’t solve the fun bits, solve the difficult bits. • A [CSS] framework should not • do your work for you, it should • allow you to do your own work faster