Hacker News new | past | comments | ask | show | jobs | submit login

I think that measuring relative numbers would make sense if we assume exponential growth. But looking at 2016,2017 and 2018, it seems to be rather linear:

https://2018.stateofjs.com/front-end-frameworks/vuejs




Fair point. I genuinely wasn't sure how to best compare it (also, I'm sure that growth slows down once a majority of users is awawre of your product, further muddying the picture).


Agreed. If I was to place a bet on which framework will grow faster over the next year, I would pick Vue.


I think React has pretty much reached saturation in terms of raw percentage. I think Vue is going to continue to erode from Angular. Also, I'd be surprised if a revised Polymer didn't see some growth since the other browsers are now starting to support a lot of the vdom features.


We have a revised Polymer, two in fact.

First is Polymer 3, which is Polymer available as standard JS modules and on npm for the first time ever. Dropping the huge barriers to usage of Bower and HTML Imports should have a large impact all on their own.

The other is lit-html and LitELement. lit-html is a template system that's much better suited to being embedded in JavaScript, and allows a very similar style and expressiveness of JSX without the VDOM overhead or a compiler. We've seen a lot of excitement and uptake of lit-html independent even of our other projects. LitElement is a Web Components base class that does async rendering with lit-html.

Given what we've seen with lit-html early adopters, I think trends will look a lot different in future surveys (even as flawed as this survey is).


Understood, I just haven't kept up with Polymer, or that much with the VDOM features in the browser, just know that a lot of those featers have started landing cross browser, and assumed that Polymer was keeping up.

I do think that if not Polymer specifically, something similar will win in the end eventually... probably something between React and Polymer. Of course Polymer will be a better model working with HTTP2 features and js modules. It'll likely come down to who gets the tooling stories worked out, or if the browsers themselves catch up first.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: