Earlier quoted context omitted.
If you pick one made by a big company, it should be fine.
That's what I thought when I integrated Google Wave into my companies workflow... /s
Google is the exception that proves the rule.
Evergreen: a React UI Framework built by Segment
111–120 of 309 posts
Re: Evergreen: a React UI Framework built by Segment
#112Earlier quoted context omitted.
React is fast. If you are not experienced in react you'll make a mess because they work against its principles. To me the Reddit web app is fast, the show part I think is the server side.
There may be some fast components in the Reddit web app, but I think there must be a valid reason why so many users are switching to the old Reddit (not just because of the way it looks, but due to performance complaints). I just went in and even scrolling through Reddit comments is laggy. Switching to old mode is like day and night.
they're sticking with the old reddit because the information density is much higher. it's a design problem.
Re: Evergreen: a React UI Framework built by Segment
#113Where can I see one page with all the components?
Re: Evergreen: a React UI Framework built by Segment
#114This 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-…
The question is: how many of these will be maintained several years later? Can you build a long term project on these? Or the expectation is that one has to make a new UI anyway every several years to keep up with the changing fashion, so rewrites are inevitable?
Jetbrains would be my bet. They'll look after it even if it doesn't become the most famous library.
Re: Evergreen: a React UI Framework built by Segment
#115This 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-…
Do any of these produce finished output that is less than a few kB, and works reliably in say the past two major versions of browsers? Bundle sizes are getting ridiculous.
Is there a React UI framework that focuses on tiny build size and browser compatibility?
Re: Evergreen: a React UI Framework built by Segment
#116This 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-…
Just clicked around and here's a note from the elastic/eui repo
" WARNING While open source, the intended consumers of this repository are Elastic products. Read the FAQ for details."
Doesn't instill confidence.
Re: Evergreen: a React UI Framework built by Segment
#117Earlier quoted context omitted.
Dependencies have cost. You have to monitor for updates, notify the maintainer(s) of any bugs, keep an eye out for security vulnerabilities, and sometimes ( gasp ) even step through them with a debugger. Doing that for one dependency is bad enough, but for 100s it's a nightmare. Personally, I prefer to just pull the pieces I need out of an open source library (unless it's very well maintained, or huge). It's like doi…
Copy/pasting has a nearly identical cost (aside from notifying the maintainer), except you have to catch all of them, you removed an easy upgrade path when other people catch the issues and you're spending vastly more time "code reviewing" every dependency you have rather than actually producing the software you're trying to write. Don't know about you, but we have actual goals and I'd never meet them if I tried your…
[deleted]
Re: Evergreen: a React UI Framework built by Segment
#118This 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-…
The question is: how many of these will be maintained several years later? Can you build a long term project on these? Or the expectation is that one has to make a new UI anyway every several years to keep up with the changing fashion, so rewrites are inevitable?
Sure, if it works now, it'll work ten years down the line as long as they're not doing anything nonstandard.
There's a big fear that projects that become unmaintained suddenly stop working; this isn't correct.
Besides, all webapps are rebuilt in a 3-5 year cycle anyway so it really doesn't matter.
Re: Evergreen: a React UI Framework built by Segment
#119Earlier quoted context omitted.
If you pick one made by a big company, it should be fine.
That's what I thought when I integrated Google Wave into my companies workflow... /s
I noticed the sarcasm, but, Google Wave never got out of beta (iirc) so anyone seriously adopting it knew what they were getting into.
Same with gmail which was in beta for years for some reason - probably because they wanted to avoid liability for lost data etc.
Re: Evergreen: a React UI Framework built by Segment
#120What I don't get: Why is it just for React?