Perf and a11y aren't the same thing. It's fine to teach a child how to cook macaroni and cheese. The perf "baseline" as it is practiced today (and evangelized by Google) makes "learning to code" a near-impossible task.
-
-
Concrete ideas like building: code splitting, tree shaking, DOM phasing, more work off the UI thread into frameworks will go much further than trying to get already-burdened curricula to cover the low level details that people can use to try to do it themselves.
-
To be concrete, I think browsers could be more overt about the fact that frameworks are likely the solution to this problem, and come clean about the fact that a vanilla.js + perf training world is unlikely to result in the fast web we all want.
-
I don't see it as one-sided. It's imo important, and OK to teach developers about a perf budget. I'd prefer not to teach them about the browser's hidden classes. I definitely think frameworks and libraries are part of the solution.
-
I think it's ok to teach devs the concept of TTI but if end devs are trying to hit frame budgets directly we probably already failed. I've met many good devs who don't even know how to use `debugger`
End of conversation
New conversation -
-
-
Re: shaming: you are right, and reading my original tweet again it really does sound like that's what I'm doing, so I deleted it. I stand by the comparison, but requires more context.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.