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

221–230 of 309 posts

Re: Evergreen: a React UI Framework built by Segment

#221

Post by Aeolun »

darekkay wrote: post #74
anonytrary wrote: post #61

Earlier quoted context omitted.

> You can, for example, pass an object {string:booleanish} and it will add only the keys whose values are truthy. Why is this something you can't do on your own in a few lines of code? const classNames = (o, c=[]) => { for (let k in o) if (o[k]) c.push(k) // booleanish return c.join(" ") } This is not cool at all! Why import a trivial function over NPM to do this for you? Better to lower your dependency count and hav…

I get the "dependency hell" issue in Javascript world, but why would I rewrite this particular utility? It's well tested (both unit and field tested), includes edge cases and has zero dependencies. As a dependency, I will also get any future bug fixes or features if I wish to. An even better example is lodash. Would you really rewrite every util you need just for the sake of not having external dependencies?

Probably because the scope is so small that you _could_ actually rewrite it yourself. And then together with all these other toy libraries, stick it in one big one that covers everything you need in terms of convenience functions.

Re: Evergreen: a React UI Framework built by Segment

#222

Post by Aeolun »

giobox wrote: post #178
bthornbury wrote: post #82

Earlier 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…

> 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 doing a code review at the same time, so you're aware of what's going on in your application. To quote yourself: Doing that for one dependency is bad enough, but for 100s it's a nightmare. 'Forking' a project's dependencies (which is effectively what this is...) is often fraught w…

I think the thing is that the one library you are forking contains 50 frivolous ones, so you’d really only be doing it twice.

Re: Evergreen: a React UI Framework built by Segment

#223

Post by naasking »

ergo14 wrote: post #212
nicoburns wrote: post #200

Earlier quoted context omitted.

Problem is, web components don't provide the same thing as frameworks like React. And the performance question still hasn't been solved. React was released in 2013, has only had minor breaking chanhes since then, and doesn't show any signs of disappearing anytime soon.

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.

Where's the benchmark showing this?

Re: Evergreen: a React UI Framework built by Segment

#224

Post by Touche »

nicoburns wrote: post #200
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.

Problem is, web components don't provide the same thing as frameworks like React. And the performance question still hasn't been solved. React was released in 2013, has only had minor breaking chanhes since then, and doesn't show any signs of disappearing anytime soon.

I don't know what you mean by "the performance question". A web component uses the same DOM APIs that React/etc. uses so it can have performance as good or better depending on how it is written.

Re: Evergreen: a React UI Framework built by Segment

#225

Post by nobody271 »

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-…

Yeah but how many of them are modern and elegant?

Re: Evergreen: a React UI Framework built by Segment

#226

Post by Aeolun »

maaaats wrote: post #55
voltagex_ wrote: post #46

Earlier quoted context omitted.

Is there a way to see what code in the project actually uses these dependencies? I gave up on learning Typescript for another 6 months after a starter template dragged in 400 dependencies.

Why would that matter for learning typescript..?

If using typescript requires 400 dependencies, it’s a non-starter, and learning it is off the table until your boss forces you to.

Re: Evergreen: a React UI Framework built by Segment

#227

Post by Touche »

Natela wrote: post #184
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 agree very much. However there are two points that make it difficult : - Virtual Dom. It simplifies a lot the creation of components. And components that are made for a VDOM are very different from those made without VDOM in mind. - Data Binding. There are multiple ways to bind data to your components, once again this might influence the way components are made. Those are not standard, some people like VDOM other n…

This is confusing. The only difference between if this were a web component vs a React component is that the consumer would not capitalize the name. Instead of `` they would do ``. That's it.

Re: Evergreen: a React UI Framework built by Segment

#229

Post by cheapsteak »

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 made a graph showing download counts of those packages on npm - https://npmcharts.com/compare/carbon-react,material-ui,antd,...

Obviously don't use that as a sole factor to determine what to go with, but with this many options, heuristics may be helpful to narrow down which ones to further investigate

Re: Evergreen: a React UI Framework built by Segment

#230

Post by pjmlp »

losvedir wrote: post #220
pjmlp wrote: post #183

Earlier quoted context omitted.

100% on mobile Web. Firefox already on beta. As for Edge it is already in development, and to be honest it doesn't matter with its insignificant market share. When Microsoft employees use only Chrome at BUILD to show Azure and .NET Core MVC features, the writing is on the wall how relevant the browser is on the market. Still you keep running away to clarify what "many browsers" means. Maybe it is my lack of native En…

> As for Edge it is already in development, and to be honest it doesn't matter with its insignificant market share. Er, really? I use Edge. It's just what's standard on the Windows machine I bought. I can't imagine that it has insignificant market share...

Check how many BUILD 2018 videos presentations were done in Chrome and how many were using Edge.

As for actual market share, http://gs.statcounter.com/browser-market-share

Post reply on HN