Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cssnext: use tomorrow’s CSS syntax, today

cssnext.io

Post reply on HN
Print view View original

21–30 of 48 posts

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

#21

Post by aquilaFiera »

menor wrote: 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.

Because you're writing standards-track CSS. That's the reason. If that doesn't appeal to you, then that's understandable. It does appeal to some, myself included.

In addition, it's built using PostCSS (meaning you can use cssnext as a plugin into PostCSS.) Using PostCSS you can achieve all of your bullet points. Today.

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

#22

Post by MoOx_ »

menor wrote: 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.

A lot of people stopped using those things. With a good methodology and a UI component approach, you will find yourself to not need mixins loops etc.

I stopped using Sass some years ago and I can definitly live without those features. Maybe one missing thing is extend, but it's comming, a CSS spec is in draft ;)

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

#23

Post by jakejake »

pcthrowaway wrote: post #17
pluma wrote: 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.

So how about all these slideshow presentations we see online (or videos of presentations, etc.) that use clips from movies, TV shows, memes, and so on? Are the copyrighted materials really necessary in those? I'd argue they're as necessary to a presentation as they are to a website, yet you never hear people on HN comment that the copyrighted material is out of place in those settings.

In some cases they probably are infringing too. But it seems worse in my opinion using copyrighted media as your main background for a promotional site. Putting a meme into a presentation slide, you may be right, it may also be legally infringement, but we kinda look the other way because it doesn't seem as promotional in nature.

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

#24

Post by Jach »

MoOx_ wrote: post #16
pluma wrote: 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.

I will keep that in mind and will update the website asap to remove those.

http://www.morguefile.com is a handy resource for finding 100% safe images.

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

#25

Post by dspillett »

pcthrowaway wrote: post #17
pluma wrote: 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.

So how about all these slideshow presentations we see online (or videos of presentations, etc.) that use clips from movies, TV shows, memes, and so on? Are the copyrighted materials really necessary in those? I'd argue they're as necessary to a presentation as they are to a website, yet you never hear people on HN comment that the copyrighted material is out of place in those settings.

They would probably come under some commonly accepted exception such as homage, humour, demonstration, reporting, and so on. The examples currently on this page the images in question are part of the page design so are functioning as part of a derived work.

Distinctions like this are rather fuzzy, but I think this sits the other side of the line most people would draw then the pages you mention.

(For reference, dear reader, in case the pages changes between me writing this and you reading it, the linked page contains stills from Back To The Future used as background images.)

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

#26

Post by bobbyadamson »

MoOx_ wrote: post #22
menor wrote: 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.

A lot of people stopped using those things. With a good methodology and a UI component approach, you will find yourself to not need mixins loops etc. I stopped using Sass some years ago and I can definitly live without those features. Maybe one missing thing is extend, but it's comming, a CSS spec is in draft ;)

Have you abandoned preprocessors altogether?

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

#27

Post by MoOx_ »

bobbyadamson wrote: post #26
MoOx_ wrote: post #22

Earlier quoted context omitted.

A lot of people stopped using those things. With a good methodology and a UI component approach, you will find yourself to not need mixins loops etc. I stopped using Sass some years ago and I can definitly live without those features. Maybe one missing thing is extend, but it's comming, a CSS spec is in draft ;)

Have you abandoned preprocessors altogether?

Yep! Some example are http://cssrecipes.github.io/ (from me & friends) and http://www.basscss.com/

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

#28

Post by MoOx_ »

pcthrowaway wrote: post #19
posabs wrote: post #4

I'm thinking about starting integrating this into my projects. However there is a couple of things that irritate me, - SASS is already serving all my needs - Current css frameworks are all on sass or less - Specs could change before CSS4 is released.

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…

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

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

#29

Post by menor »

aquilaFiera wrote: post #21
menor wrote: 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.

Because you're writing standards-track CSS. That's the reason. If that doesn't appeal to you, then that's understandable. It does appeal to some, myself included. In addition, it's built using PostCSS (meaning you can use cssnext as a plugin into PostCSS.) Using PostCSS you can achieve all of your bullet points. Today.

Of course that this can appeal to people, I'm just curious about what I'm missing. That PostCSS looks more useful to me, you're right. What is the alternative to the standards-track CSS that could benefit from this?

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

#30

Post by NathanCH »

menor wrote: 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.
Post reply on HN