3 ms·
The problem is the basic assumption that there should be a "framework" and your app is "on" it. I respect the shit out of Tom Dale, but the "megabytes aren't th
by erikpukinskis 11y ago
The problem is the basic assumption that there should be a "framework" and your app is "on" it. I respect the shit out of Tom Dale, but the "megabytes aren't that big in 2016" attitude isn't going to cut it in the long term.
Loading a web page needs to happen in a few milliseconds. Accepting anything less than that is just Stockholm Syndrome. Downloading a bunch of code that might run is antithetical to loading a web page in a few milliseconds. The path forward is treating the browser like hardware and actually only sending the hardware calls that are strictly necessary to flip the pixels you need to flip, and only fill the registers that are necessary to flip those pixels.
People like Jonathan Blow have written the web off completely because they've gotten the idea that browser makes that impossible. But it's not the browser that makes it so hard to write performant web experiences, it's the frameworks.
I'm not saying we don't need abstractions, and I'm not saying abstractions can't introduce waste. I'm saying web programmers are treating web pages like application bundles and that's not gonna work. Because there's network calls everywhere and anywhere and because the target hardware (the browser) is only fast at a somewhat quirky set of things. Lead designers and lead software architects need to get way more zen with the reality of that.
- carterehsmith 11y ago>> I'm saying web programmers are treating web pages like application bundles and that's not gonna work. Not gonna work -- just like heavier-than-air flying machines, and horseless carriages, will never work :)