Re:Web Components could replace frontend frameworks?
by spankalee on Thursday April 11, 2019 @10:28PM
(#19641413)
Performance issues? Native Shadow DOM, especially with Constructible Stylesheets, is a perf boost. Limiting style resolution to smaller scopes and less rules is good.
[ Parent
| on HN ]
Re:Web Components could replace frontend frameworks?
by lstamour on Friday April 12, 2019 @01:11AM
(#19642148)
True, I don’t have benchmarks, but there was a time period where shadow DOM was popularly disabled due to performance hits, but perhaps it was all the performance hit of polyfills and less efficient implementations in browsers. https://github.com/WICG/construct-stylesheets/blob/gh-pages/... is interesting, though Sass still looks unlikely to be added to the browser so we’ll always need some amount of CSS compilation if you want CSS nesting the way you expect it in Sass. Here’s more documentation on constructible stylesheets: https://developers.google.com/web/updates/2019/02/constructa...
I wasn’t aware of this because this stuff is being developed and released so dang quickly! (I do worry that APIs developed in relative haste might be replaced or iterated on in relative haste, especially if they aren’t adopted widely first...)
Re:Web Components could replace frontend frameworks?
by dosy on Friday April 12, 2019 @01:48AM
(#19642303)
:is()
can make concise CSS of some of what nesting does in Sasshttps://developer.mozilla.org/en-US/docs/Web/CSS/:is
there's a lot New coming into web all the time. I watch chrome status for drops.
Re:Web Components could replace frontend frameworks?
by zaphar on Friday April 12, 2019 @09:25AM
(#19644559)
Very early ShadowDom had worse performance, but the major browsers have been hard at work improving it for a while now. I haven't benchmarked in several years but I wouldn't be surprised to find that it is now a boost in many cases.
Re:Web Components could replace frontend frameworks?
by westbrookjo on Friday April 12, 2019 @11:10PM
(#19650869)
You might want to check out https://cssdb.org/#nesting-rules native nested CSS rules have hit stage 1!
Re:Web Components could replace frontend frameworks?
by lstamour on Saturday April 13, 2019 @12:22AM
(#19651113)
I checked the spec earlier and it’s impossible to make it backwards compatible with Sass without some slight edits, at least according to their GH issue on it. It’s worth watching though I suspect <style type=“text/scss”> or something like it will be added before we see broad adoption! :)
Re:Web Components could replace frontend frameworks?
by westbrookjo on Saturday April 13, 2019 @06:26PM
(#19656138)
Possibly. I think the extra `&`s are something that could wash out with one-time tooling, and that the desire for `@nest .parent &` would bump the conversion rate, but it's always fun to watch the comings and going of standards.
Re:Web Components could replace frontend frameworks?
by dfabulich on Friday April 12, 2019 @12:58AM
(#19642092)
Perf boost compared to what? It can't be a FCP perf boost relative to server-side rendered plain old CSS and HTML, because shadow DOM requires client-side JavaScript.
Plain old CSS is able to parse and render before the JS required to launch web components has even finished.
Re:Web Components could replace frontend frameworks?
by lowkeyokay on Friday April 12, 2019 @02:00AM
(#19642356)
It can be a performance boost because it only updates the part of the DOM tree that has changed. Not completely unlike React’s virtual DOM