Back to the CSS (@ToulouseJS)

Remember CSS without variables, math & friends ? Ouch. Preprocessors saved us, until we get bigger & bigger CSS to maintain. BEM saved us again to prevent crappy code, but we still need preprocessors. CSS specs, even if they are slow, will bring lots of features than will deprecate preprocessors. Will we be able to use that in 2020 ? What if we could write the same code today ?

Transcript

1. C S S
2. C S S I S O L D
3. C S S C A N N O T B E C H A N G E D
4. N O T A P R O G R A M M I N G L A N G U A G E
5. N O VA R I A B L E S
6. N O M AT H N O C U S T O M I S AT I O N
7. MAINTAINING CSS CAN BE PAINFUL
8. S P E C S A R E S L O W
9. P R E P R O C E S S O R ?
10. @ I N C L U D E
11. @ E X T E N D
13. O R G A N I S AT I O N T H E P R O B L E M I S Y O U R
14. W H AT S O U L D W E D O ?
15. .Block-element--modifier
16. VARS ? MATH ? COLOR ?
17. dev.w3.org/csswg
18. WHAT IF WE COULD GO…
19. F U T U R E S Y N TA X U S A B L E T O D AY ?
20. • C U S T O M P R O P S ( > VA R S ) • W I T H C A L C ( ) • C U S T O M M E D I A - Q U E R I E S • L O T S O F C O L O R ( ) S T U F F • M O R E ( N E S T I N G )
21. @ C S S N E X T
22. C S S N E X T F E AT U R E S A R E C S S S P E C S
23. $ npm i -g cssnext $ cssnext input.css output.css
24. P L U G I N S G R U N T, G U L P, B L U R P…
25. cssnext.github.io
27. Thanks ! @MoOx