: if $THING isn't fast enough, use something else or change the way you use it. It's that simple.
-
-
Replying to @slightlylate @nekrtemplar
It's not that simple. Client-side ends up with lots of code on the client. Server-side has latency issues.
1 reply 0 retweets 2 likes -
Replying to @sebmarkbage @slightlylate
The magical new solution is unproven. It's not that simple. You've only identified a problem, not solved it.
@nekrtemplar1 reply 0 retweets 0 likes -
Replying to @sebmarkbage
: I'm arguing for the priority of the problem in contrast to other problems. I think that's fair.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @nekrtemplar
You need to work on your narrative. It's confusing people. State the problem w/o claiming Polymer is the answer.
1 reply 0 retweets 12 likes -
Replying to @sebmarkbage
: ok: the problem is slow sites. A major cause are the architectures people TEND to use based on framework choice.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @nekrtemplar
Are you saying that Webpack is slow and should have a service-worker and codesplitting solution?
1 reply 0 retweets 0 likes -
Replying to @sebmarkbage
: webpack isn't opinionated enough to be responsible; it's a tool. Default architecture needs all of that, tho.
3 replies 0 retweets 1 like -
Replying to @slightlylate @nekrtemplar
React is just a lib. Not opinionated. Decoupling yields innovation and collaboration opportunities.
2 replies 0 retweets 4 likes -
Replying to @sebmarkbage
: yep! This is why so many of the React sites I trace are perf travesties.
1 reply 0 retweets 0 likes
: React core eng always gets to say "you're holding it wrong"
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.