3 ms·
Ah, yeah component makers are in a hard spot right now. You can't really write a 'generic' component easily and have to take a bet on using whatever JS framewo
by qbasic_forever 6y ago
Ah, yeah component makers are in a hard spot right now. You can't really write a 'generic' component easily and have to take a bet on using whatever JS framework is in vogue--react, vue, etc. It's not easy for a react project to pick up a vue component and use it or vice-versa. Even ignoring the framework incompatibilities, it also requires your component users to now buy in to the whole bundler game.
You could work around this by sticking with a generic, simpler framework like good ole jQuery. But now your framework users in react, vue, etc. are mad that they need to pull in kilobytes of JS that's doing what their framework already does.
So... as a component author a bundle of HTML and bring your own logic is kind of the only low-level option that's ubiquitous. Things might get better with web components, but it's not all there yet.
- goodoldneon 6y agoMaybe they're hoping the community creates the framework-specific implementations?
- vijaybritto 6y agoYes thats the intent. They handle only styling and framework integrations are upto the community
- aabbcc1241 6y agoIonic approaches this problem with stencil. So the ionic components can be used by not only angular projects, but also react / vue / vanilla js