kylemathews

8 ms·

31.
by kylemathews 9y ago
From the twitter announcement: https://twitter.com/reactjs/status/913797447209517056 Also this is the source for the website: https://github.com/facebook/react/blob/master/www&#
32.
by kylemathews 9y ago
Part performance and part developer experience. Gatsby generates HTML pages for each page so it loads as fast or faster than other static site generators but is way faster when clicking around the site as it prefetches pages and renders the
33.
Announcing Gatsby 1.0.0(gatsbyjs.org)
49 points by kylemathews 9y ago|2 comments
34.
Gatsby's first beta release(gatsbyjs.org)
5 points by kylemathews 9y ago|0 comments
35.
by kylemathews 9y ago
It's by Facebook. They have 1.x billion users across their web and mobile products all of which run JavaScript. Tiny improvements in product performance equals big $$$. Easily justifies efforts like this. And the rest of us get to free
36.
by kylemathews 9y ago
This is a very early release. I'm sure there'll be a "build for the web" mode soon enough.
37.
by kylemathews 10y ago
I built a fairly large backend system using event sourcing ideas and am now using Redux for another backend tool I'm building. Redux and event sourcing are very similar. One big advantage of using Redux is there's tons of document
38.
Smashing Magazine just got 10x faster – Netlify(netlify.com)
4 points by kylemathews 10y ago|0 comments
39.
Reason(github.com)
2 points by kylemathews 10y ago|0 comments
40.
by kylemathews 10y ago
Absolutely. Gatsby sites are built with React which means it's very easy to add interactive behavior in the client that communicate with a backend API.
41.
by kylemathews 10y ago
thanks Jon!
42.
by kylemathews 10y ago
Tracking shouldn't affect performance numbers much. The main problems Instagram seems to have is a) they don't server rendered HTML (so nothing shows until the client JavaScript is ready) and b) they don't use a service wor
43.
by kylemathews 10y ago
Also planning to build a "compatibility plugin" which should make upgrading pretty easy.
44.
by kylemathews 10y ago
Cool! Really happy to hear you've found it useful. And yeah... 0.x is definitely too magical. A lot of the changes in 1.0 are to make things more explicit and less magical. So even if there's a bit more typing, you'll feel mo
45.
by kylemathews 10y ago
That's definitely coming. Before the 1st beta for sure. Still ironing out a handful of core features...
46.
by kylemathews 10y ago
Absolutely. The web platform and web development tools have gotten incredibly good but can require a herculean effort to understand what's possible, how to use the tools, and get good performance. As the post points out , even instagra
47.
by kylemathews 10y ago
Definitely! I hope to write walk-throughs, etc. on how things work. (Author of post and Gatsby)
48.
Gatsbygram Case Study(gatsbyjs.org)
56 points by kylemathews 10y ago|16 comments
49.
by kylemathews 10y ago
Netlify is great for hosting static sites. Free for non-commercial sites.
50.
by kylemathews 10y ago
I love this pattern. I've been studying web performance for a while in the context of working on my project Gatsby [0] — a React.js static site generator. The next version of Gatsby is explicitly patterned after PRPL. Gatsby at build
51.
by kylemathews 10y ago
This is really excellent! I've been hoping for a while now that someone would build something like this :-) A direction that'd be interesting to explore is a guided query writer. Perhaps have a floating query input box and if you
52.
by kylemathews 10y ago
"Bandwidth" isn't the problem on 3g generally. What does cause UX problems is high latency. Speculatively precaching content is basically the only solution. FWIW, while I'm in the US so don't really understand devel
53.
by kylemathews 10y ago
Another point in favor of this model is because routing is client-side, page changes are consistently fast. In best-case network conditions, normal static sites are very fast but throw the user on a glitchy 3g network and you'll soon
54.
by kylemathews 10y ago
Sure there's diminishing returns from ~1-2 seconds page change for a DB-backed site (slower ones anyways) to the ~500 millisecond page change for a normal static site generator to the ~50 milliseconds for a React-based one but it'
55.
by kylemathews 10y ago
Javascript doesn't affect page load (generally). What Phenomic (and my project Gatsby) speed up is clicking around within a site after the initial page load as we pre-cache subsequent pages so loading those pages is near-instant.
56.
by kylemathews 10y ago
Static sites sit on a large spectrum from very simple to very complex. The nice thing about React is it works very well on very simple sites as well as very complex sites. So yes, for a very simple 5-10 pages site, using React might seem si
57.
by kylemathews 10y ago
I'm the author of another React static site generator ( https://github.com/gatsbyjs/gatsby ). I totally agree that for many sites, using Phenomic or Gatsby would be overkill. But for something small, it doesn't
58.
Typefaces: The easiest way to self-host open-source fonts(bricolage.io)
2 points by kylemathews 10y ago|0 comments
59.
Markdown-in-js: inline Markdown for React and JSX(github.com)
84 points by kylemathews 10y ago|30 comments
60.
by kylemathews 10y ago
SEEKING WORK | remote or onsite | San Francisco, CA Seeking projects pushing static sites to their limits. Offline, Service workers, AppShells, PWA, etc. Working fulltime on my open source project Gatsby ( https://github.com/

More ›