Open-sourcing the Lightning Web Components framework

Re:Open-sourcing the Lightning Web Components framework by pjmlp on Wednesday May 29, 2019 @11:41AM (#20041470)

I guess because React insists on going against WebComponents, while everyone else is adopting them.

At least that is my understanding from Angular, Vue, Ionic, Svelte and plain VanilaJS point of view.

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by hajile on Wednesday May 29, 2019 @01:08PM (#20042695)

React can be used with web components if you want.

https://reactjs.org/docs/web-components.html

The big issue is browser support. According to caniuse, IE and Edge simply have zero support while Opera and Safari have only partial compliance. The current Firefox ESR doesn't support it either (behind a flag).

The polyfill incurs a big performance hit and a lot of devs need to support those browsers for several more years.

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by pjmlp on Wednesday May 29, 2019 @02:15PM (#20043517)

Edge support is perfectly fine, and it is going to be replaced by Chrome anyway.

Firefox, Safari and Chrome based browsers are perfectly fine.

Opera is based on Bink nowadays.

ESR is not something that I regularly see in the wild.

In any case, I was speaking that only see this anti-WebComponents attitude in the React community.

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by vetinari on Wednesday May 29, 2019 @03:01PM (#20044041)

Safari doesn't support customized built-in elements, at all, and isn't going to. That is pretty far from being "perfectly fine".

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by pjmlp on Wednesday May 29, 2019 @03:36PM (#20044407)

I see all green here.

https://www.webcomponents.org/

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by vetinari on Wednesday May 29, 2019 @04:45PM (#20045248)

https://caniuse.com/#search=web%20components

The Shadow DOM and Custom Elements are not that kind of green it should be.

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by Touche on Wednesday May 29, 2019 @05:39PM (#20045825)

That's silly, customized built-ins are not an essential feature. They are a nice to have. You can get by without ever using them, which is indeed what most people do. As does the subject of this discuss, the Lightning Web Components doesn't use that feature at all.

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by vetinari on Wednesday May 29, 2019 @06:18PM (#20046221)

It also means, that you cannot use existing form controls for your custom element, you must build them up from scratch from divs, and relegate them into uncanny valley of not-quite-native, slightly-off elements.

Yes, it is possible to not use them; you can always make your life harder than necessary, you could also write an modern OS in assembly, for example, if you wanted to. If people are avoiding them today, one reason could be that they want their components to run in Safari.

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by csande17 on Wednesday May 29, 2019 @10:10PM (#20047740)

Even if you aren't able to inherit from a form element, can't you still `createElement` one and add it inside your custom element? Surely they don't force you to reimplement <input /> from scratch!

[ Parent | on HN ]

Re:Open-sourcing the Lightning Web Components framework by vetinari on Thursday May 30, 2019 @05:54AM (#20049701)

Yes, you can compose them; and then implement a proxy that creates all the methods and attributes that given element class is supposed to have and forward them to the real implementation.

Busywork, so Apple can hold their position. How nice. No, it is not "perfectly fine".

[ Parent | on HN ]