Unpopular opinion: as much as I don’t use or need React, and everything for the Web is covered by one or more libraries of mine, React goes beyond the Web.
Hermes doesn’t support classes, and Custom Elements V1 are classes based and Custom Elements, cross platform, won't "just work", likely not even with my hermes-class module, as the DOM is a foreign environment in terms of React targets.
This is something none of the libraries/frameworks you mentioned care about, but maybe the reason React is not investing much on it.
After all, ube, and its SSR counter part, are there to showcase that Custom Elements, specially without built-in extend ability, are really overrated, or not as needed as many think.
Please bear in mind, I've written more than one Custom Elements polyfill to date, and while I find their place on the Web platform a must have, also being the best primitive, in certain cases, I don't think a library targeting native platforms too should care as much as Web developers do, about Custom Elements.
Coding is as much a matter of personal growth as it is of logic and control-flow. I keep patience, curiosity, & exuberance in the same toolbox as vim and git.
*Opinions posted are my own*
Low quality comment. You are well aware of the many high-quality FP web components libraries available, and the ones you've written yourself. Read the post.
I did read the post, and maybe my arguments (already flagged as unpopular) were not mentioned?
It's easy to compare React with every other Web-only based framework (none of them work across Web and native, AFAIK), but React does something more, or something different, with different requirements (see Hermes), no other library or framework needs to care about.
If you knew me, or followed me, you'd know I've never been a React fanboy, quite the opposite, but I do admire the fact their architecture somehow scales beyond the Web, and unless we have alternatives that would work seamlessly with Custom Elements too, which are not even needed most of the case on the Web (like ube demonstrates), the comparison sounds slightly unfair to me.
TL;DR let's compare Apples to Apples, without frameworks/libraries that target only the Web platform, shall we?
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Unpopular opinion: as much as I don’t use or need React, and everything for the Web is covered by one or more libraries of mine, React goes beyond the Web.
Hermes doesn’t support classes, and Custom Elements V1 are classes based and Custom Elements, cross platform, won't "just work", likely not even with my hermes-class module, as the DOM is a foreign environment in terms of React targets.
This is something none of the libraries/frameworks you mentioned care about, but maybe the reason React is not investing much on it.
After all, ube, and its SSR counter part, are there to showcase that Custom Elements, specially without built-in extend ability, are really overrated, or not as needed as many think.
Please bear in mind, I've written more than one Custom Elements polyfill to date, and while I find their place on the Web platform a must have, also being the best primitive, in certain cases, I don't think a library targeting native platforms too should care as much as Web developers do, about Custom Elements.
Low quality comment. You are well aware of the many high-quality FP web components libraries available, and the ones you've written yourself. Read the post.
I did read the post, and maybe my arguments (already flagged as unpopular) were not mentioned?
It's easy to compare React with every other Web-only based framework (none of them work across Web and native, AFAIK), but React does something more, or something different, with different requirements (see Hermes), no other library or framework needs to care about.
If you knew me, or followed me, you'd know I've never been a React fanboy, quite the opposite, but I do admire the fact their architecture somehow scales beyond the Web, and unless we have alternatives that would work seamlessly with Custom Elements too, which are not even needed most of the case on the Web (like ube demonstrates), the comparison sounds slightly unfair to me.
TL;DR let's compare Apples to Apples, without frameworks/libraries that target only the Web platform, shall we?