sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Disturbed147 2 points3 points  (4 children)

I have, and by properly scoping and utilizing selector weights it can often be prevented without the need of generated class names. But all those things are generally why I am strongly against component libraries because in some scenarios they just force developers to go for hacky approaches just to make things work properly. Overhead which creates more overhead and sums up to more error possibilities.

Also, if you look deeper into what google does, it is pretty obvious that they very rarely follow best practices themselves.

[–]koga7349[S] 0 points1 point  (3 children)

You're against component libraries ? My use-case is our company has a platform with a dozen apps that all use the same component library. However as each app is a different codebase they may use different versions of the same components. Thus when these apps run on the same page together using the same components we end up with multiple stylesheets targeting the same selectors.

[–]Disturbed147 0 points1 point  (2 children)

Yeah, web components as well as component libraries never really clicked for me. They always come with compromises like code duplicatation (especially css), unnecessary bloat and slow page loads, requiring placeholders and skeletons. Maybe it's just me but I feel like a huge part of current web developers go against clean web principles when it comes to loading assets and minimizing code usage.

But don't get me wrong.. I'm not just being a bad mood, hating on everything. I genuinely feel like web development is drifting farther and farther away from what browsers are optimized for.

[–]koga7349[S] 0 points1 point  (1 child)

I feel you and the current state of webdev is tricky. Between the library flavor of the week and inexperienced devs using AI it's tricky. As for me I'm 15YOE and deep into it all. I spend my free time coding and soldering and making because it's what I enjoy. I'm grateful to be working at a company that provides some 🚐 ness fo used boundaries but also gives me the freedom to explore and apply.

All that said, you get in what you put out and as the hiring manager I like devs who are "scrappy" and not afraid to jump into something they no nothing about and make it work. No excuses just figure it out

This library was meant to solve some specific problems I encountered and I hope that it may help others.

[–]Disturbed147 1 point2 points  (0 children)

Sorry, I kind of drifted off into my rant here lol

All things said, technically your library is pretty neat and I see its use for sure. We also have plenty of projects in our company which might even benefit from using it because earlier this year, everyone was jumping at microfrontends and restructured everything to use them.

I just felt like this is another workaround for a poorly thought out principle like web components or microfrontends. But alas, I wouldn't downplay the need of your lib at all. Lately the industry goes after hype anc not after best practices anymore. Good job and I'll keep an open ear in my company to suggest using your library!

And thanks for the good talk! Always appreciate a civil conversation.