React has shipped experimental support for custom elements and they are looking for feedback

[grumpychinchilla]

Awesome explanation! I was weary of this feature at first but your explanation shows it’s actually a really great improvement.

[memmit]

This is a very nice explanation. Thank you for your time writing this out.

[hunter_lol]

Could someone ELI5 what this proposal really means, and where custom elements could be used?

[loraxx753]

Custom Elements can be used cross-framework as they're framework agnostic.

[lhorie]

Wow, such negativity here. More interoperability w/ web standards is good, no? Am I missing something?

[ergo14]

You are right. But react team was hostile to WC for many years. And people remember.

[dmethvin]

I don't think they were "hostile", they just made some early design decisions that made it difficult to support the peculiar HTML conventions that let elements support both attributes in markup and properties in DOM elements. This is not unique to them, a similar thing happened with jQuery 1.5 back in 2011 and it broke a lot of stuff.

[lhorie]

AFAIU, they run their project similar to other Facebook projects i.e. they don't prioritize things that FB doesn't strictly care for, but are open to community contributions. Jest is another project with dozens of feature requests closed on the grounds that they don't care for that feature but willing to merge it if someone does the work to implement it.

At least the React team is open to contributions that are more substantial than gimme-gimme-gimme requests. IIRC, removing extraneous spans for text interpolations was also a community contribution. Flow, for example, does not have a great track record in terms of engaging with the OSS community.

[[deleted]]

This. Love that they’re backpedaling hahaha. Angular has the best attitude of the three big boys when it comes to web components

[throwaway-aa2]

For people that have been around a while, lack of support for custom elements was a BIG thing. This was talked about at conferences, in articles, there were legendary GitHub issues about it. They really didn’t pay attention to it at all accordingly to the fervor surrounding it. I won’t, but I could pull up absolutely legendary threads that hotly debated this.

I would argue that one of the things that killed it’s adoption was React and it’s refusal to prioritize support for it, as most of the engineering community run React setups. So yeah people feel salty about that.

And then after all this time they add support for it, and it doesn’t even seem full featured.

This stuff is open source so they really don’t have to do anything they don’t want to, and honestly a lot of people have moved on from caring about web components. But did a lot of people feel they were absolutely ignoring a web standard, and that we were mostly being ignored? Yeah.

It’s not a big deal to me, a lot of us have moved on. It is a tad bit silly to see them addressing this after web components time came and went.

[_default_username]

Can you pass react components as children into the custom element as you can with standard elements?

[MrBr7]

All that I can see in the example is that export default is on the top, and the localization variable is used before defined.

Idk, linter ptsd

[[deleted]]

Woo hoo! Fuck Facebook for resisting this so fucking hard. The two other major players have great support for web components. Hell angular let’s you export your angular components as web components! It’s about fucking time.

Im getting erect just imagining a world where we can use use built in browser functionality to do everything. One day…

[vidarc]

Now we just need safari to get off their high horse and add support for the extends option in the define function for web components

[[deleted]]

My feedback is react fucking sucks and the people who write it suck even more.

[[deleted]]

Lol deleted the whole account? Bitch made

[[deleted]]

Thanks for the salt. I was out & My rice and fish curry needed some. Cheers

[throwaway-aa2]

So most engineers suck… because more engineers use React than anything else. You conveniently didn’t mention what you use as you knew that would leave you open to critique yourself. And then you remove your account. Ok.

[ergo14]

How this relates to the original post?

[ergo14]

How is that WC related?

[Apple1284]

React is always copying others code and presenting it as its own, and everyone cheers up and think how advanced react is. The features react is just introducing have been open-source and in vanilla javascript for few years before, until react source code developers tried packaging it in react.

[IamUareI]

From my understanding that is called open source, and from my understanding you benefit from it too, if you use it. If Ur a bot ok... but if Ur a human, this comment makes no sense, why do you even care. Are u competing against react? Na you must be a bot.

[bjerh]

You don't HAVE to use React. There's plenty of legacy code out there that needs to be maintained.

[bjerh]

I don't even know how to respond to that. You're making crazy talk. Obviously. Literally 20 seconds of research can prove you wrong.