Re:Web Components Aren't Framework Components
by nesarkvechnep on Monday December 11, 2023 @03:50AM
(#38598794)
Refined the concept into the simplest form that works… as long as you have JavaScript enabled.
[ Parent
| on HN ]
Re:Web Components Aren't Framework Components
by lelanthran on Monday December 11, 2023 @05:18AM
(#38599227)
What's the alternative other than simply doing without this feature?
Re:Web Components Aren't Framework Components
by Quekid5 on Monday December 11, 2023 @06:40AM
(#38599726)
E.g. Apache's Server Side Includes[0] allows for
<!--#include virtual="/footer.html" -->
Tbf, you did specify 'server language' in a post further up the comment chain, but the the thing is that it doesn't have to be much more complicated that SSI -- assuming it's available for your deployment target, of course.(SSI obviously does not require JavaScript.)
Re:Web Components Aren't Framework Components
by lelanthran on Monday December 11, 2023 @07:50AM
(#38600193)
I've used those before, but I feel that having something that works within the spec, independent of any particular implementation's extensions is much more valuable for longevity.
Sure, you can use $A if using $B server, or use $C when using $D language, or use $E when using $F framework, or use $G when using $H reverse-proxy, or use $I when using $J CDN, or use $K when using $L hosted cloud service ...
Or you can just use what's in the specification which works on all of the above, but won't work on clients with Javascript disabled.
It's a "choose your poison" scenario.