- Good for you :)
- You probably don't need a framework
- There is no such things as CSS 4 http://www.xanthir.com/b4Ko0 . That said, cssnext will handle features like babeljs, using different stages. An issue is opened for this https://github.com/cssnext/cssnext/issues/100
"You probably don't need a framework"
Care to explain? And how does babeljs fit in?
Re:Cssnext: use tomorrow’s CSS syntax, today
by pcthrowaway on Thursday May 28, 2015 @11:22AM
(#9618763)
I took a look at cssnext while going through the source for the 'Solved by Flexbox' website which was front page last week (https://github.com/philipwalton/solved-by-flexbox/). It looks like it does a lot of what sass does, except that it will actually be CSS soon. I suppose it's kind of like using an ES7-to-ES5 transpiler rather than using some other compile-to-JS language; it's a matter of preference, but the ES7 will eventually run without dependencies as well when the transpile step is no longer needed.
It'd be nice to see CSS frameworks rewritten using pure CSS (transpiled with cssnext); in fact I might give it a try if I get motivated :)
Check out http://cssrecipes.github.io/ (from me & friends) and http://www.basscss.com/
http://www.basscss.com/docs/base-buttons/
Perhaps shouldn't be asking here, but why does a button element get a different style than .button links and inputs?
I like the idea of this library, but that's not leaving a good taste in my mouth.
Re:Cssnext: use tomorrow’s CSS syntax, today
by neilhem on Thursday May 28, 2015 @11:09AM
(#9618656)
Sass not SASS http://sassnotsass.com/
- SASS is already serving all my needs
- Current css frameworks are all on sass or less
- Specs could change before CSS4 is released.