It feels like there is some weird incentive on the Google Chrome team such that they will give us infinity incredibly great tools to measure the performance of web apps but they put $0 towards research and dev of real-world frameworks to use those tools to figure out how to improve perf of userland applications. Like, great, you invented a flame graph but I don't know how to use it, can you give me a best-practice code sample instead?
Like I realize the Chrome team's job is narrowly to *work on Chrome* but the *reason* they do that is that a faster web is better for Google's bottom line, so you'd think some investment in the latter would meet their goals.
@seldo Isn't that basically the reason that web.dev exists? To highlight all the stuff that they do that exists (mostly) in the Chromium ecosystem
@mcneely Is *that* what it's for?
@seldo I mean that's how I've always looked at it. Helpful yes, but certainly not 100% altruistic.
