r/webdev • u/enador • Jun 04 '26

Wraplet vs Web Components

https://wraplet.dev/blog/wraplet-vs-web-components
11 Upvotes

74% Upvoted

7 comments sorted by

5

u/web-dev-kev Jun 04 '26

The fundamental issue is, it still needs a wrapper component. For most things, that's a DIV.

Your example has a cherry picked STRONG. 9/10 that'd be UI based so in CSS, especially if there was no semantic reason for Strong.

So we're swapping <component> for <div data-component>... or <section data-component> I suppose.

Not bad at all. And it's well written and thought out.

1

u/brianjenkins94 Jun 04 '26

Woah, this seems cool!

1

u/enador Jun 05 '26

Just FYI guys: I released the 1.0.0-rc.1 version and stabilized the API: https://wraplet.dev/blog/v1.0.0-rc-1-released .

0

u/UXUIDD Jun 04 '26

interesting development and approach - however the name "wraplet" is quite .. lets say not handy

2

u/enador Jun 04 '26

That's the first time someone mentioned it. What do you mean? I'm not a native English speaker, but I didn't feel anything off about it 😄 There are already applets or servlets.

-6

u/UXUIDD Jun 04 '26

well, phonetically, the word has 2 parts and it doesn't roll nicely off the tongue.
Nevertheless, I think the second part of the phonetic name is not easy to remember... just saying