ergo14

17 ms·

121.
by ergo14 8y ago
People were saying that about jquery too. Vue is gaining a lot of traction too. This year it is STILL react being the one with biggest userbase, but that might not be true in a year or two. This discussion pops out every once in a while, IM
122.
by ergo14 8y ago
Yup, notice that from the slack screenshot that I posted it has speed mark 1.18 that puts it before Vue in terms of speed (which makes it plenty fast IMO, and its not even stable yet), I never claimed it is the fastest one of the bunch. Nic
123.
by ergo14 8y ago
Wow - 60kb for cookies is crazy.
124.
by ergo14 8y ago
Yes, but the website is not only for polymer elements, you can find components written in other libraries too, like lit, svelte or even vue. That's what I meant - it is just a website that serves as information aggregator from bower&#x
125.
by ergo14 8y ago
That was my point, we should not need to rewrite this over and over.
126.
by ergo14 8y ago
https://stefankrause.net/js-frameworks-benchmark8/table.html - thats old lit release there vs react 16 (react pre 16 would be slower and everyone agrees its generally fast already), on slack channel I believe I saw ne
127.
by ergo14 8y ago
Well, FX 63 ships next week, and Edge update their roadmap from considering to implementing: https://twitter.com/kylealden/status/1047240569439711232 . So Edge is the only browser missing 100% native support right
128.
by ergo14 8y ago
I think you confused multiple things together - why do you bring webcomponents.org the website into discussion, it has no relation here. Web components are a low-level primitive - they are clunky to use directly. Polymer and LitElement - ar
129.
by ergo14 8y ago
Lit-html is faster than react + vdom - and has 6kb instead of 60kb. And back in the time everyone used jquery, the arguments are always the same.
130.
by ergo14 8y ago
What do you think youtube, ing, netflix, or EA properties use? ;)
131.
by ergo14 8y ago
Their roadmap was JUST updated, do probably few months.
132.
by ergo14 8y ago
https://github.com/webcomponents/webcomponentsjs - all frameworks use same polyfill. https://github.com/vuejs/vue-web-component-wrapper "You will also need the Shady DOM + Custom Elements pol
133.
by ergo14 8y ago
Yup, Polymer is "big" dependency, but with things like svelte, litelement or stencil you can build web components which have little overhead. Also polyfills are separate thing from polymer - they are reused by ALL other frameworks
134.
by ergo14 8y ago
Edge is implementing (updated the roadmap), Firefox ships enabled WC's in closest release (it is already in the beta) I think Firefox 63 will ship in a week?. That leaves only IE11/Edge with polyfills.
135.
by ergo14 8y ago
I think rewriting UI systems every few years and reimplementing in various JS frameworks that come and go is a serious waste of manpower. I'd so wish people would embrace web components properly once and for all, with LitElement, Svelt
136.
by ergo14 8y ago
Great, another UI framework that will not work with Vue, Marko, Angular, LitElement or basicly anything else than react. When will the trend stop :/ Can't we embrace web components already and have those UI frameworks work in all
137.
by ergo14 8y ago
Please point me to paragraph that says something like that.
138.
by ergo14 8y ago
What you just wrote makes no sense, I have no idea how you came to that conclusion.
139.
by ergo14 8y ago
I don't get why this would be an alternative - those two can and should supplement eachother.
140.
by ergo14 8y ago
I don't get why this would be an alternative - those two can and should supplement eachother.
141.
by ergo14 8y ago
D'Hondt method led to this outcome.
142.
by ergo14 8y ago
Vue looks nice, but nowdays I'd pick something like lit-element(lit-html) or stencil.
143.
by ergo14 8y ago
It is worth noting that Pyramid Web Framework is also awesome to use. I see it as a middle ground between Django and Flask. The scaffolds make some design decisions for project and you can pick from what you like the most. Pyramid allows fo
144.
by ergo14 8y ago
Exactly, that is my problem, if a react component state is altered by "outside world", weird things can happen. So you actually avoided interoperability between solutions.
145.
by ergo14 8y ago
Did the "foreign" elements stamp out react elements or interact with their properties?
146.
by ergo14 8y ago
Thing is react is only compatible with react ;-)
147.
by ergo14 8y ago
Up till not long ago pipenv was not ready - for example it could not install packages like gevent. That bug is fixed now I believe.
148.
YouTube page load is 5x slower in Firefox and Edge than in Chrome(twitter.com)
4 points by ergo14 8y ago|1 comments
149.
by ergo14 8y ago
With lit-element you get native elements that are similar to react elements. And only parts of the dom that changed actually do mutations - like with vdom. https://github.com/Polymer/lit-element#minimal-example
150.
by ergo14 8y ago
Yes, because between jQuery and react there was nothing in between, and functional programming or singletons for state were unheard of. /S On other hand you still have things broken in react not to mention few years with uncertain pate

More ›