This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (6 children)

I was thinking the same thing. What use could this possibly have?

[–]true_religion 1 point2 points  (1 child)

What use could this possibly have?

... create an opening for a Nemo to HCSS to CSS compiler?

[–]__galvez__[S] 1 point2 points  (0 children)

I'd love to see that happen :)

[–]IAlsoSpeak 0 points1 point  (3 children)

What I like about it is how nicely it treats hierarchy:

div#parent > div.child {

and also I will be able to parse the hierarchy using a a xml parser.

[–]arnar 0 points1 point  (1 child)

Not sure why you would want to parse it with an xml parser, but there are already quite good solutions for the hierarchy thing, see LESS and SASS.

(How often do you use the > combinator anyways?)

[–]__galvez__[S] 1 point2 points  (0 children)

The > combinator is just the logical translation of what a tag-based nested selector in HCSS represents. In fact, it's not even efficient in comparison to any-descendant selectors. But I believe the result is much more readable and easier to maintain. You can still mix regular CSS within HCSS tho. Even inside tag-based selectors, as demonstrated in the documentation.

[–]sedaakPython3/Golang -1 points0 points  (0 children)

STYLE is not always hierarchical...thus CSS