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

Native HTML elements with CSS superpowers

native-elements.dev

Post reply on HN
Print view View original

11–20 of 31 posts

Re: Native HTML elements with CSS superpowers

#11

Post by jjcm »

rsoto wrote: post #10

Isn't it slower querying elements via attributes? Whenever I find a «brand» new way to work with CSS (or whatever they wanted to call it), I'm skeptical. Most of the times they just redo what IDs and classes were made for, but way worse. While this might have good intentions in mind, it's just adding classes via attributes. Also it's explained very badly, I had to click three buttons in order to get examples.

It used to be. In modern engines it's really no longer the case. Just did a mini test running both attr and class name selectors on 10000 objects. In both instances the paint was fully complete in a single frame.

Agree with the rest of the stuff you've said though. I just don't see a place for this library.

Re: Native HTML elements with CSS superpowers

#12

Post by kroltan »

I read the whole documentation and I have absolutely no idea what this is, besides something about CSS?

The best information there is is by going to the last two tabs in its Theme Builder, which makes me think this is some sort of CSS framework. But the GitHub boldly denies that, so I have no idea.

Re: Native HTML elements with CSS superpowers

#13

Post by syspec »

I think a lot of the pushback against this library, is in how it is marketing itself.

On the homepage, you cannot tell what it is (i clicked around as well, still no idea). It looks like it is a CSS framework, but it claims it is not without clarifying what it is.

For many engineers, myself included, that ticks all the wrong boxes thus making it under deliver if it is not the greatest thing since slice bread.

Re: Native HTML elements with CSS superpowers

#14

Post by dubcanada »

jjcm wrote: post #11
rsoto wrote: post #10

Isn't it slower querying elements via attributes? Whenever I find a «brand» new way to work with CSS (or whatever they wanted to call it), I'm skeptical. Most of the times they just redo what IDs and classes were made for, but way worse. While this might have good intentions in mind, it's just adding classes via attributes. Also it's explained very badly, I had to click three buttons in order to get examples.

It used to be. In modern engines it's really no longer the case. Just did a mini test running both attr and class name selectors on 10000 objects. In both instances the paint was fully complete in a single frame. Agree with the rest of the stuff you've said though. I just don't see a place for this library.

I mean you are right, but there are certainly selectors which are "faster" just the faster part is more on the 0.000001ms level than any measurable level.

Also I am fairly certain (been a while since I spent time in Webkit source) but class name and attribute selectors are implemented the same, if you want to do a proper benchmark you would want to do id, nested selectors, attributes, class, etc. And at that level you will find a significant difference.

Re: Native HTML elements with CSS superpowers

#15

Post by wilsonrocks »

jjcm wrote: post #11
rsoto wrote: post #10

Isn't it slower querying elements via attributes? Whenever I find a «brand» new way to work with CSS (or whatever they wanted to call it), I'm skeptical. Most of the times they just redo what IDs and classes were made for, but way worse. While this might have good intentions in mind, it's just adding classes via attributes. Also it's explained very badly, I had to click three buttons in order to get examples.

It used to be. In modern engines it's really no longer the case. Just did a mini test running both attr and class name selectors on 10000 objects. In both instances the paint was fully complete in a single frame. Agree with the rest of the stuff you've said though. I just don't see a place for this library.

I could see the point in attribute selectors - when using react I find it messy to programmatically specify class names based on state/props, particularly when using BEM.

Setting some Booleans as attributes is much nicer. However, it is built into CSS already, so not sure a library would help...

Re: Native HTML elements with CSS superpowers

#16

Post by wilsonrocks »

izietto wrote: post #9

What are the advantages over using data attributes instead of classes in order to style HTML elements?

I think where you have several Boolean states an element could be in, it can be nicer that programatically constructing a string with the required classmates in.

Re: Native HTML elements with CSS superpowers

#18

Post by sumnole »

illumanaughty wrote: post #5

The homepage tells you nothing about what this is. Even if I go to the GitHub I get "Native Elements (NE) is not a CSS framework"...great so what is it?

As far as I can tell, it's a class-less css framework

There was a good thread on these a few weeks ago: https://news.ycombinator.com/item?id=23220081

Re: Native HTML elements with CSS superpowers

#19

Post by DoctorOW »

illumanaughty wrote: post #5

The homepage tells you nothing about what this is. Even if I go to the GitHub I get "Native Elements (NE) is not a CSS framework"...great so what is it?

It looks like it generates a classless CSS file based off settings you give it? Someone can correct me.
Post reply on HN