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

231–240 of 309 posts

Re: Evergreen: a React UI Framework built by Segment

#231

Post by losvedir »

pjmlp wrote: post #230
losvedir wrote: post #220

Earlier quoted context omitted.

> 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

Hm, maybe I missed the context somewhere along the lines. Are you talking about something on the developer side only? I thought the discussion was about something that works or not for the end user.

Re: Evergreen: a React UI Framework built by Segment

#232

Post by marpstar »

mobilefriendly wrote: post #154
marpstar wrote: post #43

Earlier quoted context omitted.

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

Can you elaborate on how this works? Thanks!

Gladly. Blueprint provides all of the "components" and I use Basscss to lay them all out in responsive containers.

I use Basscss' grid and flex helper classes to define how my I can create a 3-column responsive layout with something like:
There's also a couple of other helpers like `max-width-*` which ensure responsiveness as the screen grows larger. Things like adding the `Classes.FILL` (which causes a button/control to go full width of its container) are useful for making things seem more like mobile (where buttons often are full width of the device, minus padding)

All in all, while it's a slight bummer than Blueprint isn't just responsive out of the box, I haven't really found that to be a deterrent to getting things done.

Re: Evergreen: a React UI Framework built by Segment

#233

Post by 49para »

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.

heh, I've worked for companies that hit the max on cookie size (which I think is around 60kb). For an entire framework to be 60kb would be amazing for these companies :)

Re: Evergreen: a React UI Framework built by Segment

#234

Post by virtualmic »

laurent123456 wrote: post #160
virtualmic wrote: post #145

Earlier quoted context omitted.

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

My connection is fast enough too. I'm on Firefox though, so maybe that's the "issue", if their framework is designed to work mostly on Chrome and not the other browsers.

Yes, I am looking at it in Chrome on Ubuntu.

Just tried it in Firefox 62 on Ubuntu. Works good there too.

Re: Evergreen: a React UI Framework built by Segment

#235

Post by ernsheong »

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…

Try https://github.com/Polymer/lit-element for an alternative to VDOM, without the VDOM part. It's reactive and uses lit-html under the hood.

Re: Evergreen: a React UI Framework built by Segment

#236

Post by ergo14 »

naasking wrote: post #223
ergo14 wrote: post #212

Earlier quoted context omitted.

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?

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 newer release benchmarks that are better (it also depends at which specific test you look at).

New version of repeat is interesting:

https://slack-files.com/T03PF4L4C-FCY51FZAB-c2fcf32931

Re: Evergreen: a React UI Framework built by Segment

#237

Post by ergo14 »

no1youknowz wrote: post #176
ergo14 wrote: post #133

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 popular solutions out there? Every time something new comes out existing solutions are being rewritten from scratch.

I suppose since it's open source, then there is nothing stopping anyone from porting it to Vue?

That was my point, we should not need to rewrite this over and over.

Re: Evergreen: a React UI Framework built by Segment

#238

Post by ergo14 »

Eli_P wrote: post #217
ergo14 wrote: post #215

Earlier quoted context omitted.

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…

Thanks for links you provided. Don't know what you mean by saying it has no relation; I've been using that site for searching components while developing my PWA based on Polymer. I can install components with yarn or npm just fine, using instructions and examples from there.

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/npm.

Re: Evergreen: a React UI Framework built by Segment

#239

Post by naasking »

ergo14 wrote: post #236
naasking wrote: post #223

Earlier quoted context omitted.

Where's the benchmark showing this?

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 newer release benchmarks that are better (it also depends at which specific test you look at). New version of repeat is interesting: https://slack-files.com/T03PF4L4C-FCY51FZAB-c2fcf32931

I compared my usual candidates: vue, inferno, Surplus and vanillajs, and lit-html was dead last overall in almost every category. Also slower than Preact now that I checked, so I'm not sure that performance benefits are one of lit-html's unique strengths.

Re: Evergreen: a React UI Framework built by Segment

#240

Post by ergo14 »

49para wrote: post #233
ergo14 wrote: post #212

Earlier quoted context omitted.

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.

heh, I've worked for companies that hit the max on cookie size (which I think is around 60kb). For an entire framework to be 60kb would be amazing for these companies :)

Wow - 60kb for cookies is crazy.
Post reply on HN