The JS community has sold itself a huge pile of tools that, on average, don't work.
-
-
I mean, the "work" in the sense that you can make them do something that can run on a fast computer.
1 reply 0 retweets 1 like -
But the modern JS/Framework community is ungrounded; never before have so many applied such long toolchains for such poor results.
1 reply 3 retweets 7 likes -
What kills me is that I can't follow this thread up with links to a dozen traces (which I have) because it would be punching down.
2 replies 0 retweets 1 like -
Developers were sold a bill of goods; it's not entirely their fault that their tools are bad-by-default where it matters most (mobile).
1 reply 0 retweets 0 likes -
And the major framework authors are ducking their responsibilities in ways that are opaque to most.
1 reply 0 retweets 0 likes -
Nobody talks about the 2 week (or month) perf sprint they had to add to their launch to get to minimally usable.
2 replies 0 retweets 0 likes -
Do you think it is possible this comes from relying too much on DX and not truly responsive designs? Even new t is for desktops only.
3 replies 0 retweets 1 like -
Replying to @coderitual @slightlylate and
I even heard "This way I don't have to even touch the DOM"
2 replies 0 retweets 2 likes -
Replying to @g33konaut @coderitual and
I keep teaching basics like event delegation, semantic elements, etc.
2 replies 0 retweets 2 likes
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.


