Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Evergreen: a React UI Framework built by Segment

evergreen.segment.com

Post reply on HN
Print view View original

141–150 of 309 posts

Re: Evergreen: a React UI Framework built by Segment

#141

Post by pjmlp »

Cthulhu_ wrote: post #118
dmortin wrote: post #30

Earlier quoted context omitted.

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.

Do you feel like rewriting a bunch of webapps written in Perl/modapache around early 2000?

I know of at least one company with such a stack. Just like I know others with Web Forms, Stucts, SEAM, JSP, Zope and many other stacks in production.

Not everyone re-writes their webapps, specially in companies where software is a cost center and totally unrelated to their main business.

Re: Evergreen: a React UI Framework built by Segment

#142

Post by pjmlp »

quickthrower2 wrote: post #114
dmortin wrote: post #30

Earlier quoted context omitted.

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.

Jetbrains is the new Borland, but I hope that their management doesn't come up with an Inprise idea.

Re: Evergreen: a React UI Framework built by Segment

#143

Post by apoorvgarg »

breytex wrote: post #139

Does anyone knows a react ui framework which also includes concepts for more high-level interfaces? Not only atoms and molecules, but also "organisms" and "pages" as a compound of several components? I feel like, a lot of ppl still create horrible UIs based on good components, because they lack the bright overview.

This might be useful https://github.com/ant-design/ant-design-pro

Re: Evergreen: a React UI Framework built by Segment

#144

Post by anonytrary »

jhall1468 wrote: post #107
anonytrary wrote: post #77

Earlier quoted context omitted.

This is a trivial function, your argument applies to complex utilities. It is piss easy to roll your own, and it's not worth introducing a potential attack vector via a new dependency. In this case, if your devs can't keep up with your classNames function, fire them, because it's trivial. it("should work with no classes", () => { expect(classNames({}).to.be.false }) it("should work with a single class", () => { expec…

If you write 100 ~50 line "trivial functions" you've now written 5000 lines of code that doesn't actually solve your underlying problem, it just makes it slightly easier. And you can't write this particular utility function in 5 minutes and support all the uses-cases, particularly if you are going to write a bunch of unit tests. The reason to depend on someone else's code in trivial use-cases is entirely because they…

> If you write 100 ~50 line "trivial functions

No, we're talking about 2-3 line functions. Stop arguing with a straw man. You're taking what you know to be true about complex code, and then asserting that those things are also true with simple code. That doesn't work.

> And you can't write this particular utility function in 5 minutes and support all the uses-cases

The beauty is that because we are rolling our own function, we only need to support the single function signature we decide we're going to stick to in our codebase. Supporting every use-case becomes a moot point.

The author of the library has to support the 10^5 people who use his code, meaning he's more likely to merge silly pull requests like "should take objects", "should flatten the input array", "should allow multiple arguments", "should work with X", "should do Y" because people have different styles.

> The reason to depend on someone else's code in trivial use-cases is entirely because they are trivial. There's nothing you're doing aside from wasting time by writing it

It only takes time if you are not able to do basic programming. I find basic programming to be a much more enjoyable and productive approach than depending on potentially dozens of trivial libraries whose APIs are not the way I would design them, and could change at any time. Learning dozens of APIs takes just as much time as implementing them for a certain set of functions. That set is different for everyone, but it is not the null set for anyone.

Re: Evergreen: a React UI Framework built by Segment

#145

Post by virtualmic »

laurent123456 wrote: post #102

That's a minor thing but when I press the back button on one of the documentation pages it takes 6 seconds to go back (first it changes the title of the tab then it seems to wait for 6 seconds, probably parsing and running several MB of JavaScript). Sometimes the tab titles is blinking and displaying "Evergreen" and "Components - Evergreen" very quickly during these 6 seconds. You'd think in 2018 going back to a page…

This doesn't happen for me, it is pretty quick. I am in India and on a 40 Mbps connection.

Re: Evergreen: a React UI Framework built by Segment

#146

Post by pjmlp »

ernsheong wrote: post #63

I wish people would stop making UI frameworks in , and instead make it web components based with vanilla JS/very light lib dependency, so that everyone can enjoy the benefit. React is becoming a bubble of its own, and it's exclusive.

I am on the same boat, hence why I am on Angular and Polymer side.

Everything else that builds their little platform on top of the browser is not interesting to me.

Re: Evergreen: a React UI Framework built by Segment

#147

Post by pjmlp »

aikah wrote: post #128
ernsheong wrote: post #63

I wish people would stop making UI frameworks in , and instead make it web components based with vanilla JS/very light lib dependency, so that everyone can enjoy the benefit. React is becoming a bubble of its own, and it's exclusive.

Web components are not supported in many popular browsers. Until they are widely supported they are not a thing. And no, Polymer and co are not polyfills for them, they are their own incompatible frameworks. I agree in principle but it's up to browser vendors to implement specs, and it is always the same offender that is dragging his feet.

Edge and Firefox are only missing Shadow DOM and Custom Elements, which they are already developing.

On mobile Web 100% of the browsers support Web Components.

https://www.webcomponents.org/

So what are the many popular browsers you refer to? As anything else is meaningless.

Re: Evergreen: a React UI Framework built by Segment

#148

Post by pjmlp »

Vinnl wrote: post #90
ernsheong wrote: post #63

I wish people would stop making UI frameworks in , and instead make it web components based with vanilla JS/very light lib dependency, so that everyone can enjoy the benefit. React is becoming a bubble of its own, and it's exclusive.

Yeah, I really dislike Polymer's approach of using Web Components as an architectural pattern, but this is the exact use case they're good at. Then again, I can understand that you don't whip something like this up in a day, and support for Web Components might not be as widespread yet as a UI framework author would like.

There is 100% support on the mobile web across Safari and Chrome.

Re: Evergreen: a React UI Framework built by Segment

#149

Post by arvinsim »

ui-explorer12 wrote: post #20
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-…

I looked at many of these for an assessment at my company. We started a little broader with some css-only solutions as well but they tend to only take you so far; the controls are nice. Key aspects for us were (1) React-based, (2) TypeScript support (bonus for native TS), (3) Applicable to data-dense engineering apps, and (4) a broad-based, healthy ecosystem. I also evaluated Semantic-UI React. I really like Blueprin…

I tried both BlueprintJS and Ant Design on two different projects I am handling.

While BlueprintJS is more intuitive, I find that it lacks a lot of built-in components compared to Ant Design.

Re: Evergreen: a React UI Framework built by Segment

#150

Post by arvinsim »

marpstar wrote: post #43
nemothekid wrote: post #42

Earlier quoted context omitted.

I'm in a similar boat as you. We actually started building on top of Ant. However, we first started out by building out our Admin pages and they were built with Blueprint. I like Blueprint a lot more than Ant, but Blueprint doesn't pretend to support responsive applications[1], which was somewhat important to us. Blueprint exposes a couple building blocks (like PopOver) which really help in building more custom funct…

I've been using Blueprint and pairing it with Basscss for some responsive assistance and it's been successful (and a lot of fun).

I will look into this since I am on BP3 on a project and it seems that they will eventually want responsive support.
Post reply on HN