Dinosaur.js

June 24, 2016

Craig Freeman, Sean Michael, Chris Pruyne, Marie Schmidt

"Making it better without making it over"

Rebecca murphey

aka Refactoring

growth is not necessarily bad, but growth without a strategy for managing it is

package.json

analytics

  • What's important?
  • What will be bad if it's broken?
  • What are key actions that a user can take?

takeaways

It's unrealistic for you... to learn a framework that solves a problem you've never experienced

Every technology decision is eventually regrettable

Framework or no, JavaScript growth is unbounded in the absence of constraints
Education is a powerful enabler
Teaching how to care and what to care about is immensely transformative

takeaways

Building for the web is better today

links

"Server farm to table:

HOW THE INTERNET WORKS"

Jenna Zeigen

(the good parts)

overview

  • IP Address Lookup
  • Opening a socket
  • Security
  • HTTP request/response
  • Parsing
  • Rendering

http/1.1

hypertext transfer protocol

  • Requests / responses
  • Delivers "hypermedia"
  • Released in 1999 (a dinosaur, in web terms)
  • Limited connections per origin
  • Requires "creative" workarounds

http/2

highlights

  • Multiplexing
  • Header compression
  • Stream priority
  • Server push

http/2

fun facts

  • Finalized in February 2015
  • Requires secure connection
  • Browser *and* server must
    be on board
  • Current v1.1 workarounds
    may hurt

http/2

how can i prepare?

  • Stop concatenating files
  • Stop making sprites
  • Stop inlining images
  • Stop domain sharding
  • Move connections to TLS

http/2

going forward

  • Focus on caching behavior
  • Organize assets by component
  • Keep using CDNs
  • Continue minimizing size of requests/responses

http/2

the early years

links

DinoJS Recap

By Craig Freeman

Loading comments...

More from Craig Freeman