github.com/GoogleChrome/sw-toolbox and github.com/GoogleChrome/sw-precache to help simplify writing and maintaining service workers #ChromeDevSummit

  • 0
  • 1

  1. @IBMFrontend at #ChromeDevSummit

    • 1
    • 5

    1. Client storage is the largest loading perf win in all browsers #ChromeDevSummit

      • 0
      • 0

      1. Cost of actually using the network docs.google.com/a/snug.ug/document/d/1f2tcvW72A9haFkCNsVhKgi1iteNrCRHYA7Y_uIautl4/mobilebasic #ChromeDevSummit

        • 0
        • 0

        1. Sad so many examples are being given via framework code. 3 lines of framework code doesn’t mean anything to complexity #ChromeDevSummit

          • 0
          • 0

          1. Browser storage quotas per domain #ChromeDevSummit

            • 2
            • 0

            1. Reasoning about browser storage and when domains get evicted #ChromeDevSummit

              • 0
              • 0

              1. V8 mission statement #ChromeDevSummit

                • 5
                • 4

                1. History of measuring performance #ChromeDevSummit

                  • 1
                  • 1

                  1. Real web page runtime breakdowns in V8 #ChromeDevSummit

                    • 1
                    • 0

                    1. Status of Service Workers today #ChromeDevSummit

                      • 0
                      • 0

                      1. Server render vs single page app. Missing here is that the critical rendering path is at end of render (green) #ChromeDevSummit

                        • 0
                        • 0

                        1. Server render provides gradual render, single page apps break that. When streams land, that will minimized #ChromeDevSummit

                          • 0
                          • 0

                          1. Server rendered pages can often be faster than single page apps. SPAs need everything before they render, slowing them #ChromeDevSummit

                            • 0
                            • 0

                            1. Progressive Web App does not mean Single Page App #ChromeDevSummit

                              • 1
                              • 0

                              1. You don’t need to wait to add PWA functionality to your site. Leverage progressive enhancement and you can start today! #ChromeDevSummit

                                • 0
                                • 0

                                1. Automatically generate a web manifest from your rendered HTML webmanife.st #ChromeDevSummit

                                  • 2
                                  • 1

                                  1. A bunch of preprocessor available as web workers. Very cool. github.com/patrickkettner/WebWorkerPreProcessor #ChromeDevSummit

                                    • 0
                                    • 2

                                    1. Link to all the goodies @jaffathecake talked about jaffathecake/797235127835246592 #ChromeDevSummit jaffathecake/797235023673892864

                                      • 1
                                      • 2

                                      1. The CSS Houdini slides from the #ChromeDevSummit breakout. Lots of great coming here. DasSurma/797250746034991104

                                        • 0
                                        • 2

                                        1. SLICE the web.

                                          Secure Linkable Indexable Composable Ephemeral

                                          #ChromeDevSummit

                                          • 0
                                          • 2

                                          1. Or its the web SAD NUCLEAR MICE #ChromeDevSummit

                                            • 1
                                            • 2