The 2016 Web Development Workflow – Google I/O 2016


Matt Gaunt and Sam Saccone on The 2016 Web Development Workflow In this session, we will take a retrospective look at old workflow tools, future web tooling …



  1. Constructive feedback guys, I had to stop watching at 6 minutes. Don't try to be funny if you're not funny. People have come to this video to learn not hear bad jokes which even in the first 6 minutes got in the way of anything you were trying to say.

  2. this talk was complete, total crap… their message is this: use standards over tooling whenever you can… "embrace the platform"…. ugh…. kill me now. 10 seconds of info decompressed into 40 minutes.

  3. Great thesis. Horrible presentation.

    Thesis: thanks for pointing out that the languages we write in are alive. They grow and become more expressive as the years go on, and as slang enters our dictionaries. There's a temptation in web development to let the tools snowball and to become caught up in all the extraneous things without realizing that the language itself is growing.

    Presentation: don't get infatuated with the way you present something to the point that you distract from what it is you're trying to present. Your talk is constantly being derailed by awkward laughs at what you drew, how someone said something, etc. Remember good comedians don't laugh at their own jokes. We didn't come here for your presentation, we came for your idea. Next time focus on what you need to say and don't get caught up in how you say it—especially not if you're getting caught up in details that are insignificant to your message or if you're getting caught up in things that are negative (how badly done something is, how someone did or said something "wrong"). The latter is especially bad for your audience, because it confuses us regarding your credibility.

  4. I wonder if there's scope for the (eg) css-next process to be integrated with the web server – since it knows (presumably) what the browser is and what it supports, and if it needs to add polyfills into the JS and/or prefixed css/etc to the css (and perhaps even replace some modern html with simpler equivalents of old). Then the developer doesn't have to rebuild their app when more browsers support the features.
    Someone must have done this already, right?

  5. at the end they say, we should develop against the newest features and then only send poly-fills for the exact features that the current browser does not support, but they give no solution how to do this: are there some tools that can help – or is this only part of the "suspended reality"?

  6. Great Talk !
    I absolutely loved it, content and form : keep up spreading the word.
    Convincing developers to use a deployment workflow over development workflow is one of the hardest thing to do nowadays, but it's essential if we want our platform to succeed in the mobile space.
    Thanks 🙂

  7. The problem with the talk was It took a really long time to actually start, the humor i don't mind, albeit a bit cringy.. Like 9 minutes in you actually start talking "stuff".

  8. I think you overdid the humor a little, specially with the "babel" thing. Also, don't interrupt each other please.
    But I think it began picking up at the end, and the point you make is good! We should question ourselves if we really need a tool before using it.

  9. I want to use web-starter-kit in my company but I need to replace SASS with PostCSS and replace Gulp with JakeJS first (just because Gulp still uses deprecated dependencies).

  10. toi den hang sony giup va hoi nhung dieu can ban cua he dieu hanh day la khi cung hon 2nam roi hang sony cho toi sem tat ca nhung chuec dien thoai cua hang va ser cam nhap cho toimot quon sach toi doc toi chi ngo la cuan sach do noi ve hai anh em va nguoi nauy