Live data from Hacker News

Cssnext: use tomorrow’s CSS syntax, today

cssnext.io

41–48 of 48 posts

Re: Cssnext: use tomorrow’s CSS syntax, today

#41

Can I run this in-browser without the command line? LESS is very easy to get started with - just include less.js and a developer can start writing LESS right away: http://lesscss.org/#client-side-usage-browser-options - anything similar for cssnext? Does cssnext support source maps? This is an important feature for any non-trivial project, as it lets a developer inspect how the rules in the source language are transl…

cssnext has some features that LESS doesn't like auto prefixing CSS rules according to your browser scope. So it rely on caniuse database which is why it's not a good idea to use it on the client side. That being said, there is a playground so you can try it http://cssnext.io/playground/

SourceMap is supported, see options http://cssnext.io/usage/#sourcemap

Re: Cssnext: use tomorrow’s CSS syntax, today

#43
post #13

I looked into this for my current project, but in my opinion you have to leave behind too many things if you do this instead of Sass. Namely: -No mixins -No maps -No loops and conditionals Maybe a couple of years ago, but now that libsass runs so fast I still don't see the point of using this.

Perhaps more importantly no support for partials. But I guess your task runner can deal with that.

You can totally support partials. By default, csssnext inline @import directive. Like all css processors.

Re: Cssnext: use tomorrow’s CSS syntax, today

#44

I'd recommend getting a native English speaker to proof-read your text. 'More faster' was used repeatedly on the page and should be simply 'faster'. There were a few other typos, (e.g. 'A bug fixed will be released ASAP.') and very non-idiomatic sentence constructions. It might be a solid undercarriage, but now's the time to polish the hood. Also, I'd def. remove the movie screenshots. You could still use imagery tha…

I've fixed the mistakes you mentionned and removed copyrighted images.

Re: Cssnext: use tomorrow’s CSS syntax, today

#45

I'd recommend getting a native English speaker to proof-read your text. 'More faster' was used repeatedly on the page and should be simply 'faster'. There were a few other typos, (e.g. 'A bug fixed will be released ASAP.') and very non-idiomatic sentence constructions. It might be a solid undercarriage, but now's the time to polish the hood. Also, I'd def. remove the movie screenshots. You could still use imagery tha…

I've fixed the mistakes you mentionned and removed copyrighted images.

Re: Cssnext: use tomorrow’s CSS syntax, today

#48
post #20
post #11

Earlier quoted context omitted.

That's not how copyright works. You don't have a license for those images, so you can't use them. Period. Fair use only applies under certain circumstances where using copyrighted materials is necessary (e.g. satire or discussion). Even if you don't use them commercially, you can't just use them like that.

Nothing in the 4 criteria implies necessity. http://en.wikipedia.org/wiki/Fair_use#Fair_use_under_United_...

Yes. It's a simplification.

Necessity isn't a criterion for fair use, it's the reason fair use provisions exist in the first place.

Making satire of or discussing a copyrighted work without using copyrighted material is extremely awkward if at all possible. Internationally speaking (i.e. aside from the specific definition of fair use in US law), necessity is a good rule of thumb, just like profit/non-profit use.

Post reply on HN