About a year ago.
Kenneth, tell them about RemoteDebug
RemoteDebug.org
Our web development workflow.
Where does our editors fit?
Today's webplatform.
The browser is our application runtime
The evolution of our tooling.
Browser tooling.
Blackboxes.
IE Developer Toolbar
Firebug
Chrome & Firefox DevTools
Dogma.
What about our workflow?
It hasn't really changed.
Typical bug-fixing workflow
Reality.
= our web development workflow is completely broken
What have we done to fix it?
Fixing the symptoms with more tools.
More tools.
Adding more complex workflows.
LiveReload workflow
Introducing new prototyping tools.
JsBin, CodePen, JsFiddle and many others
DevTools becoming your editor.
Chrome "Studio"
What does it mean?
Does this mean that the browser vendors are on their way to compete with the editor vendors?
Stop.
Our assumptions are wrong.
Reality.
Application runtime.
We live here.
Disconnect.
What do we need?
Keep our editors being editors, and let’s integrate.
A more sane workflow
I think deep integration between our editors and browsers is the key to better a webplatform.
What's happening?
Emmet LiveStyle
Microsoft BrowserLink
Stop stop stop.
Inventing proprietary protocols.
Remote debugging protocols.
Remote debugging protocols
The RemoteDebug project
RemoteDebug vision
Why the Chrome protocol?
Documented + integrations
Like Lighttable and Brackets
Kenneth, bash the Chrome team.
Some good news!
Kenneth, show them the Mozilla tweet and announcement.
Kenneth, tell them about V8 and Node.
The open web follows standards.
Our tools should too.
Thanks.