Skip to content

Research

Greg Slepak edited this page Oct 14, 2016 · 5 revisions

Elm

Related to #99.

Also:

Review Twitter's switch back to server-side architecture

https://news.ycombinator.com/item?id=4040929

Service Workers?

Useful for offline web apps.

From: https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md

We can use service workers:

From: https://jakearchibald.com/2014/using-serviceworker-today/

ServiceWorker is a background worker, it gives us a JavaScript context to add features such as push messaging, background sync, geofencing and network control.

In terms of network control, it acts like a proxy server sitting on the client, you get to decide what to do on a request-by-request basis. You can use this to make stuff work faster, offline, or build new features.

And:

With the ServiceWorker, we get to first-render over a second faster, and our first render includes images, which takes 16 seconds without ServiceWorker. They're cached images of course, but ServiceWorker allows us to present a fully-rendered view while we go to the network for latest content.

Documentation?

If our documentation for devs starts getting unwieldy, take a look at some of the doc gen stuff out there: