Re:Web Components Will Outlive Your JavaScript Framework
by mdhb on Wednesday October 25, 2023 @12:51PM
(#38014893)
The v0 part of it should mean none of that was a big surprise. It was an early prototype, it’s stable now.
Re:Web Components Will Outlive Your JavaScript Framework
by svieira on Wednesday October 25, 2023 @02:41PM
(#38016590)
v0 (IIRC) was not called v0 when it was released. It was called "custom web components". The release of a new version of custom web components is what caused the re-name to `v0`, with the new version being called `v1`. So you built on top of one version to be told later that you'd participated in a beta (unbeknownst to you).
Re:Web Components Will Outlive Your JavaScript Framework
by ble on Wednesday October 25, 2023 @08:27PM
(#38020139)
hmm. doesn't stuff like this happen every time that chrome implements some interface but other browser vendors don't get on board with that specific version? doesn't this happen... kind of often? isn't it apparent that there's a risk of this happening whenever chrome implements something before there's standards agreement?
Re:Web Components Will Outlive Your JavaScript Framework
by troupo on Thursday October 26, 2023 @01:21AM
(#38021894)
> doesn't stuff like this happen every time that chrome implements some interface but other browser vendors don't get on board with that specific version?
Yes. What rarely happens though is that Youtube gets immediately rewritten with the new tech.
That already happened.
HTML Imports got deprecated (in favor of a JS-only solution), though Firefox already implemented them.
Custom Elements v0 was deprecated even though Chrome implemented it and hastily re-wrote Youtube with it. They had to wait ~4 years to remove the implementation because it took Youtube that much to switch.