I can't stress enough how much server-side practices & assumptions set you up for failure on the client side.
-
-
Replying to @slightlylate
It was, in some ways, better when "serious developers" derided (and feared) HTML/CSS. The client was left to folks who respected the limits.
2 replies 4 retweets 15 likes -
Replying to @slightlylate
Think you may be over-stating your case. Web development has never produced better web applications than it is now.
1 reply 0 retweets 2 likes -
Replying to @AdamRackis @slightlylate
Saying the payload may be a bit bloated at times misses the forest for the trees.
1 reply 0 retweets 0 likes -
Replying to @AdamRackis
: not just talking about webdev. We see the same thing w/ folks showing up w/ server-side C++ chops and flailing. Client is hard.
2 replies 1 retweet 3 likes -
Replying to @slightlylate
: on server, your static initializers might hurt your app startup a bit, but how often do they start? On client, can be critical.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: e.g., at some point in '09 we went on a rampage to eliminate all SI's because they tanked Chrome startup. Massive win.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: similarly, who cares how many .so's (or DLLs) your thing is made of on the server? On the client, that's seek-time & YOU LOSE.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: but the key in both cases was doing what the JS community seems not to do much today: respecting low-end hardware's limits.
4 replies 0 retweets 2 likes
: so, I'd agree with your "best apps" statement on the condition it's preceded with: "On $2K+ laptops & $600+ phones..."
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.