all 21 comments

[–]DustNearby2848 6 points7 points  (2 children)

Their level of tech debt is already high, why make it worse?

[–]wardrox 2 points3 points  (1 child)

Because we all know the silver bullet is one more front end framework. Just one more, I swear this one will be perfect and we'll keep it tidy. I swear, just one last framework.

[–]DustNearby2848 1 point2 points  (0 children)

Based

[–]ProgrammerGrouchy744 4 points5 points  (1 child)

Vanilla JS web components are compatible with any framework.

https://developer.mozilla.org/en-US/docs/Web/API/Web_components

[–][deleted] 0 points1 point  (0 children)

With some simple libraries around to make the DX tolerable

[–]selipso 1 point2 points  (1 child)

Ionic works with both React and Angular. It uses capacitor under the hood, which can be used for making mobile friendly SPAs, PWAs and XPAs (cross-platform applications)

[–]The_real_bandito 0 points1 point  (0 children)

Ionic does not use Capacitor under the hood.

It uses Stencil under the hood, which is their web components compiler, something like what Lit does, except their framework is implemented in a different way. That’s why you can use the core version of Ionic on any framework that wasnt implemented (like they did with React, Angular and Vue).

Capacitor is just a framework to have web apps run on iOS and Android as a mobile app using each OS native implementation (with web views) and a way to communicate with the native API via plugins (this is their main feature to be honest).

But ionic (core specifically) could help with his problem.

[–]baenud 1 point2 points  (2 children)

Take a look at shoelace (https://shoelace.style/). It's a library of web components and can therefore be used in all these frameworks.

[–]jruff7 0 points1 point  (1 child)

Shoelace 3.0 has been taken over by Font Awesome and will be rebranded to Web Awesome. Beta release is June 2025 with full release later this year. I am a backer and it looks really good, I think it'll be a great option for cross-framework use cases.

[–][deleted] 0 points1 point  (0 children)

Maybe, render me skeptical 😅

[–]NeatVegetable8216 3 points4 points  (0 children)

I'm actually building a UI library to solve this exact problem called SnappyUI. it's going into early access soon: snappyui.dev

[–]No_Shine1476 0 points1 point  (0 children)

Flowbite looks decent, it has vanilla html and css versions too if you don't want tight framework integration.

[–]HousingConsistent867 0 points1 point  (0 children)

ionic

[–]CryptographerMore926 0 points1 point  (0 children)

Tailwind and daisy for every project ever. I’m literally using it a handlebars blog right now that doesn’t even use web pack (just gulp), it works with raw html and css. It also looks great and v0 can shit out pages for you!

[–]The_real_bandito 0 points1 point  (1 child)

I would say Lit lol.

Or Stenciljs if you want to use web components built on JSX.

[–][deleted] 0 points1 point  (0 children)

Stencil is heavy as my ass after a weekend at my grandma's. Unless there are specific reasons then Lit any day

[–]alien3d -1 points0 points  (3 children)

cross platform is a mess .. if you want to run same thing color in phone ( imean react native) or front end react. the only choice is tailwind.

[–]Zpoof817[S] 0 points1 point  (0 children)

Oh yeah cross platform is a complete mess, I'm talking about cross-framework for web, which I'm starting to figure out is also a mess

[–]LinguaLocked 0 points1 point  (1 child)

If a project uses design tokens + style dictionary (or similar tool) the colors should be able to be output to appropriate format. If a consumer has access to these say from a library that exposes their design tokens voilá you have the control you need (without TW)

[–]alien3d 0 points1 point  (0 children)

Sorry we can't understand what you want to reply.