ndreckshage

Joined 13 years ago

Karma

89

Submissions

32

Member since

Jan 22

View on Hacker News

Recent submissions

Comment · 8 years ago

I'd be really interested in adding Twitter (etc) support to Lumenette with help of Keybase, if possible. Hoping there will be an API for other wallets to interact with the features Keybase is working on.

I've been using Keybase git and file storage for some time now. Really excited about this partnership!

Lumenette wallet, for reference: https://galactictalk.org/d/1159-lumenette-android-ios-stella...

Comment · 9 years ago

what theme is used in the screen shots?

Comment · 9 years ago

Next is great. I would love to deprecate my SSR starter kit - Sambell - https://github.com/humblespark/sambell - once it supports a layout file, for animated transitions, etc. Right now, React Router seems fundamentally more powerful as a SPA framework.

Comment · 9 years ago

Comment · 10 years ago

Really nice work with all this! Great blog post on update

Scalable reducer management and data fetching for React-Router/Redux github.com

13 ndreckshage 10 years ago 0 comments

Comment · 11 years ago

Next best - http://www.techrepublic.com/article/pro-tip-dim-your-ios-scr...

FrontendPerformance frontendperformance.com

3 ndreckshage 11 years ago 0 comments

Comment · 11 years ago

Correct, not rendering on the server removes the bottleneck.

Comment · 11 years ago

Still relies on JavaScript server side rendering - which will be the biggest performance bottleneck, by far, for both this and React.

If you really want a framework that is faster, check out Tungsten (https://github.com/wayfair/tungstenjs), which is as fast as this client side, and can render in vanilla Mustache using Go/C++.

Comment · 11 years ago

Blanket statement: anyone that makes blanket statements like 'React sucks' or 'Ember sucks' should not be taken seriously.

Comment · 11 years ago

This mentions using Node/Express to help with concurrency. Ok. But this also mentions using 'isomorphic' javascript with React, and also not completely reliant on cache. React.renderToString (and all other isomorphic options -- Rendr, etc) are synchronous and slow. (rendering a large page in React w/ static data would take ~600ms; whereas the same page with with Mustache in Go for example would take ~30ms). End result, decreasing concurrency, and hurting overall performance.

OP - can you shed any light on how this is actually impacting your performance? Or maybe things that you had to do to get around the problem (ex - details of 'module level' cache with Redis etc).

Comment · 11 years ago

Everyone is copying everyone. Grow up.

Comment · 11 years ago

Confidence in returning the minimum to render a view. By default, without having to worry about over / under fetching data. Not having to worry about cleaning up endpoints when the needs of the consumer changes. A client that requests exactly what it needs, rather than hitting an endpoint with 'something', is extremely efficient.