Cssnext: use tomorrow’s CSS syntax, today

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 :)

[ Parent | on HN ]

Re:Cssnext: use tomorrow’s CSS syntax, today by MoOx_ on Thursday May 28, 2015 @11:52AM (#9618969)

Check out http://cssrecipes.github.io/ (from me & friends) and http://www.basscss.com/

[ Parent | on HN ]

Re:Cssnext: use tomorrow’s CSS syntax, today by webXL on Thursday May 28, 2015 @01:27PM (#9619674)

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.

[ Parent | on HN ]