Evergreen: a React UI Framework built by Segment

Post by pier25 » Wed, Oct 17, 2018, 12:45 PM UTC

chrisco255 wrote: post #73

matsemann wrote: post #54

Earlier quoted context omitted.

While I agree React isn't the issue here, you chose horrible examples. Loading Facebook on my computer (especially trying to open a chat window) brings my computer to a knee. And using twitter on mobile browser you quickly learn how the spinner looks.

I haven't had performance issues on Facebook in quite some time. And Twitter works like a charm on my Nexus. I'm wondering how much of your issues have to do with either round trip latency or network issues.

Post by evrydayhustling » Wed, Oct 17, 2018, 12:51 PM UTC

ianhawes wrote: post #10

This list was posted a few weeks ago, but here is a fairly definitive list of similar UI frameworks: https://element.eleme.io/ https://ant.design/ https://quasar-framework.org/ https://at-ui.github.io/at-ui/ https://developer.microsoft.com/en-us/fabric https://vmware.github.io/clarity/ http://appnexus.github.io/lucid/ https://ng-lightning.github.io/ng-lightning/ https://blueprintjs.com/ http://www.jetbrains.org/ring-…

Post by ergo14 » Wed, Oct 17, 2018, 12:57 PM UTC

Eli_P wrote: post #205

ergo14 wrote: post #162

Earlier quoted context omitted.

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, Svelte or Stencil. This way we won't have to live with another framework-bootstrap clone again and again and everyone can contribute to one solution that will work with all JS frameworks.

It seems replication of numerous UI frameworks to be a fruit of Evolution per se, and it will happen again and again. You named Web Components, I've been embracing them for a while, but if you tried to switch from Google's Polymer to LitElement it wouldn't go smooth as you could have imagined. Both Polymer and LitElement are based on Shadow Dom and WC features curated by Google, but are not 100% backward compatible.…

Post by Eli_P » Wed, Oct 17, 2018, 1:08 PM UTC

ergo14 wrote: post #215

Eli_P wrote: post #205

Earlier quoted context omitted.

It seems replication of numerous UI frameworks to be a fruit of Evolution per se, and it will happen again and again. You named Web Components, I've been embracing them for a while, but if you tried to switch from Google's Polymer to LitElement it wouldn't go smooth as you could have imagined. Both Polymer and LitElement are based on Shadow Dom and WC features curated by Google, but are not 100% backward compatible.…

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 - are libraries - you can author WC's with them. And yes they are different (I used both), but you don't really have to migrate from one to another. Web components are not divided - Li…

Post by ksrm » Wed, Oct 17, 2018, 1:13 PM UTC

pier25 wrote: post #210

Natela wrote: post #191

Earlier quoted context omitted.

React is not fast, clearly the simple idea of having a virtual Dom is very costly compared to do things by hand. However for a large scale app react makes it more easy to reason about and keep it maintainable, components are far easier to implement, etc... So for many people, the benefits you get on the development side outweight the performance overhead

There is an overhead, but the main problem with the new Reddit is not that it was made in React, but that it's a massive fuckup. Not only from a programming perspective but also design and UX.