@slightlylate I know you are old time so landscape might be different but what did you do?/what do you recommend if one were to start building now?
-
Show this thread
-
Replying to @kosamari
Back in The Day (TM), we worried about file size but CPUs and networks were continuously improving. The big challenges were getting to a uniform API and stagnant trailing-edge browsers.
1 reply 1 retweet 5 likes -
Replying to @slightlylate @kosamari
Today we have the inverse: stagnant CPUs and networks, but rapidly improving software in the lowest-perf environments.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @kosamari
So what we did back then was to build abstractions in the absence of browser progress and count on CPUs, networks, and JS VMs to get faster to deliver more functionality under the same budget
1 reply 0 retweets 1 like -
Replying to @slightlylate @kosamari
The new world is topsy-turvy: we can afford to burn CPU and network time to make up for the deficiencies of old browsers; the wealthiest users have the worst runtimes. Crazy! You can spend $1K on a phone and get a browser that's years behind.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @kosamari
...and that same phone has a CPU that 2-5x faster than the competition and is usually on a much, much faster network.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @kosamari
You get what you pay for. Sort of. Ish. This is a very strange timeline. ANYWAY. My advice for new frameworks is to lean as hard as you can on the platform (spoiler alert!).
1 reply 1 retweet 5 likes -
Replying to @slightlylate @kosamari
...and then transpile/polyfill for The Olds (TM). On average, they can afford it, but the folks on the most modern runtimes can't.
1 reply 1 retweet 3 likes -
Replying to @slightlylate
I found "how browsers work" talk you gave in 2011(!) that went into chromium source code, was part of learn the platform also learning internal of browser ?
1 reply 0 retweets 2 likes -
Replying to @kosamari
Yep! About the same time, Tali Garsiel was publishing her research which opened this up to a wider audience: https://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ …
1 reply 0 retweets 0 likes
By that time (Summer '11), we were deep into the Parkour project, designing large parts of ES6 + Promises, Web Components, and tons of CSS stuff.
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.