Recent searches
Search options
Administered by:
One of the best off the cuff videos on #WebComponents and the madness of #React and its tradeoffs #webDevelopment
https://youtu.be/1vF6puwX3bE?si=iXnjEJ2JJtUZzA7Y
@jerryD I would go entirely framework-less for little stuff and #WebComponent libraries - it's a great future-proof solution. Add the recent #CustomElements #LSP made for #Neovim, #Intellij or #VSCode into the mix - a cherry on top!
But for everything beyond that, like #MPA, #WebComponents make a good neighborhood with #Astro or #HTMX for me.
@vintprox interesting perspective. Never heard of Astro and I'm pretty meh on HTMX.
I've built moderate sized apps with Web Components and the experience has been great. Also, if GitHub, ING bank, parts of Reddit, Google Earth, YouTube, Photoshop Web can be successfully built via Web Components, then I'll be fine. I think there's nothing I'll ever build that can't be built using the technology.
Nothing beats not having to think about breaking changes and convoluted build steps (though I bundle and minify my web components).
Web Components + Shadowdom + CSS Module Scripts + JSON module scripts have made web development fun again. Can't wait for HTML module scripts.
@jerryD Haha, this second from last part is the gist of my conflicted introduction to web components: gotta bundle those things that were supposed not to be the part of the problem... unless I am just mistaken about their purpose.
HTML modules are a showrunner of bundle-less to me. Can't seriously do something big without yet another system in place to gather all in one.
@vintprox there's no requirement to bundle nor minify web components. For whatever reason, a lot of developers opt to not bundle and minify web components. I do because it benefits the application.
@jerryD That's kind of their appeal: so open and readable that you don't have to dig deeper. All up until you find that rotten apple among them that wants to look extra slim and obfuscated...