I
I
ivanovSP2017-10-27 10:19:53
JavaScript
ivanovSP, 2017-10-27 10:19:53

Will Web Components kill frameworks?

Will Web Components kill existing frameworks (react/vue/angular)?
What is the probability that something new will come out, i.e. fourth framework.
Who has an opinion?
https://developer.mozilla.org/en-US/docs/Web/Web_C...
+
https://habrahabr.ru/post/229189/
+
https://developer.mozilla.org/ru/docs/ Web/JavaScript...

Answer the question

In order to leave comments, you need to log in

3 answer(s)
K
Konstantin Kitmanov, 2017-10-27
@k12th

With WebComponents, the problem now is that the support for component technologies is very fragmented, and polyfills weigh shamelessly and are not complete.
polymer?

D
Dima Pautov, 2017-10-27
@bootd

Well, "Web Components" will not be soon. Besides, here as always. In js, everything that is added is rarely used in its pure form. Most often, people write wrappers. I think that these components will simply migrate to the same react, vue and the like. And everything will be the same, but under the hood there will be a native implementation of the components. If, again, they will compete in flexibility with what is in the frameworks. I read somewhere on Habré that native components are still far from ideal

S
Sergey, 2019-09-19
@ferocactus

One day, for sure. Soon? Unlikely. In the end, I'm sure that all the functionality currently implemented in the "libraries" will be included in the standard. "Libraries" are crutches created to close the shortcomings of the standard.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question