Jordan Brennan
Never heard of inert attr.
It seems that you can use it like this:
<div inert={isInertOn ? "": undefined}/>
github.com/WICG/inert/issues/58
But yes, React compiles to html so dev must rely on the compiler support.
I don't often use Web Components but I agree that is a shame that an industry leader library lacks in fundamentals.
It seems that something is moving here
github.com/facebook/react/issues/11347
Is a shame that an industry leader library lacks in fundamentals.
This is a weird thing, hard to accept honestly, even if 95% of apps never encounter these problems it doesn't mean that these should be ignored.
Great points here Jordan.
I find Vue’s Single File Components with Options API to be the easiest to learn, design, code, and test. Its simplicity compared to React or even Vue’s own Composition API is way more valuable than all of React’s exotic stuff that at the end of the day doesn’t help you achieve anything new. It’s just more code and goofy rules to work around. Also, Vue’s real HTML and CSS trump React’s XML abomination and total lack of support for component styles too.
The final nail in React’s coffin is its persistent incompatibility with web standards. To this day it is not fully compatible with Web Components and fails, and has failed many times, to handle certain HTML attributes correctly. If your web framework struggles to work with HTML that’s kind of a sign right?
I have years of experience with both and would choose Vue over React always.