It IS an invalid question! but people make the assertion that XYZ framework is to blame for their woes.
-
-
Replying to @samccone
: I got into something related at the front of my I/O talk: https://www.youtube.com/watch?v=a5X_Ot-R6lo … /cc
@jaffathecake@stefanpenner1 reply 0 retweets 5 likes -
Replying to @slightlylate
: which is, roughly, that our tools and frameworks make expensive things appear cheap at dev time /cc
@jaffathecake@stefanpenner1 reply 1 retweet 6 likes -
Replying to @slightlylate
: it's unclear who is at fault for being that far down the primrose path, but situation is *bad* /cc
@jaffathecake@stefanpenner1 reply 0 retweets 1 like -
Replying to @slightlylate
: put another way, if people actually tested on devices, most frameworks wouldn't have a market /cc
@jaffathecake@stefanpenner4 replies 11 retweets 33 likes -
Replying to @slightlylate @samccone and
What? Are you seriously getting behind that statement?
1 reply 0 retweets 0 likes -
Replying to @mcardleliam
: I've been profiling a lot of apps over the past year, so yes, I am /cc
@samccone@jaffathecake@stefanpenner2 replies 0 retweets 1 like -
Replying to @slightlylate @samccone and
Maybe in a academic bubble this can ring true…for real users, performance isn’t bad.
2 replies 0 retweets 0 likes -
Replying to @mcardleliam @slightlylate and
This is like saying, if people profiled their apps they would never use ruby or python.
2 replies 0 retweets 0 likes -
Replying to @mcardleliam @slightlylate and
There is a point where performance is good enough and other concerns are more important.
1 reply 0 retweets 1 like
: the issue here is that "fast enough" on the client is a much, much harder problem
/cc @samccone @jaffathecake @stefanpenner
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.