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

31–40 of 48 posts

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

#31

Post by Wintamute »

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.

The point of using it is to get back to native CSS, and restrict yourself to features that improve simplicity, adaptability and architecture of large CSS code bases.

Using a nice component based architecture (perhaps like SUITCSS) and this you can write really maintainable CSS, that can be understood by everyone, now and in the future, not just those that have learnt Sass.

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

#33

Post by webXL »

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

- 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

#34

Post by webXL »

MoOx_ wrote: post #28
pcthrowaway wrote: post #19

Earlier quoted context omitted.

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/

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

#35

Post by artmageddon »

MoOx_ wrote: post #18
selfsimilar wrote: post #10

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…

Thanks for reporting that. I am french and the website is really fresh (pushed this morning). I will do my best to improve it and remove images.

In the part with, "Why cssnext?" there's "Prior 2015", which is sorta correct but might be better worded with "Before 2015," or "Prior to 2015"...

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

#36

Post by nightpool »

Jach wrote: post #20
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.

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

Its a simplification, and not a very incorrect one. The purpose of Fair Use is to reserve for society those uses that benefit society more then they hurt copyright owners. Whether a use is "necessary", while not a legal definition, is a pretty good rule of thumb for some possible Fair Use defenses.

ETA: also this is completely ignoring any relevant international laws. French law, which is where the OP lives, appears to provide some protections for "necessary" use.

"The Court of Appeal disagreed and applied French law. Nevertheless, it too rejected plaintiff's claim and decided that Google benefited from the "safe harbor" provisions of the Loi sur la Confiance dans l'Economie Numérique [the relevant French statute]. It considered Google as being a "neutral" actor and the reproduction of the photos necessary to provide the service."

http://cyberlaw.stanford.edu/blog/2011/01/who-said-france-do...

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

#37

Post by DanBC »

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.

> yet you never hear people on HN comment that the copyrighted material is out of place in those settings.

Some parts of HN don't make that kind of meta style comment because it's off topic for HN. But here it's a risk for the site owner - DMCA could remove their site - and so people mention it.

There are people who could mention copyright at every applicable opportunity and I'm glad that they don't. (Although I would like a place for that kind of comment! Also, tpyos).

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

#38

Post by menor »

Wintamute wrote: post #31
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.

The point of using it is to get back to native CSS, and restrict yourself to features that improve simplicity, adaptability and architecture of large CSS code bases. Using a nice component based architecture (perhaps like SUITCSS) and this you can write really maintainable CSS, that can be understood by everyone, now and in the future, not just those that have learnt Sass.

Using a nice component based architecture and Sass you can also achieve the same, for me is more maintainable changing a key value in a map and having a new type of button generated than having to copy/paste the rules. And I think learning Sass is not that difficult if you already know css.

Not having lots of nested divs with lots of class names also helps to code readability and maintainability if you use something like React with JSX.

I see advantages in not needing to precompile in the future, but apart from that I see this as a step back, of course it's my opinion, I see how this can work for other people.

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

#39

Post by untog »

neilhem wrote: post #14
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.

Sass not SASS http://sassnotsass.com/

Who cares?

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

#40

Post by leepowers »

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 translated into the rules read by the browser. Support for source maps in Chrome Developer Tools makes a workflow much more efficient: https://developer.chrome.com/devtools/docs/css-preprocessors

Post reply on HN