Building Chrome DevTools with Vanilla Web Components

An airhacks.fm conversation with Jack Franklin (@Jack_Franklin)
about: A thick, chunky Dell Laptop, Playing Tycoon, creating a
soccer website with DreamWeaver, learning PHP and CSS, learning
python, Java and prolog at the university, writing Rails code, the
popularity of Ruby on Rails, Python vs. Ruby, switching from
Angular to React, Angular 1 vs. Angular 2, backward compatibility
and React, React Hooks, hooks vs. lifecycle methods, starting at
Google Chrome Dev Tools Team, working on Chrome Performance
Insights, Chrome Dev Tools is a Web Application, from custom
framework to Web Components and lit-html, Chrome SDK manages state,
Polymer was chatty, lit-html is a tagged template literal, lit-html
performs partial updates, the bar for using frameworks gets higher,
lit-html optimises the rendering, console.begin and console.end for
better developer experience, lit-html is used in Chrome, what
happens if FaceBook looses interests on React, what is the worst
case scenario for loosing a dependency, using Chrome's ninja and
rollup.js for bunding, Chrome supports import maps, chrome
-custom-devtools-frontend storybook for WebComponents, adding
JS-comments with JSDoc for type annotations for better refactoring
in plain ES 6, any and unkonwn in typescript, Performance Insights
panel lowers the bar for website optimizations, the Chrome Recorder
generates pupeteer script, the Recorder panel is also implemented
with Web Components, big UI features are implemented as Web
Components, Jack's post: "Why I don't miss React: a story about
using the platform",

Jack Franklin on twitter: @Jack_Franklin, Jack's blog
jackfranklin.co.uk