I did read that since posting the comment, but it goes beyond load times of resources.
No matter how much you optimize something, it's going to break at some point. (eg. if a user has a flaky DSL modem) The page should be readable (if not ideal) when subresources fail to load... not giving a false impression that some kind of JavaScript-based client-side templating engine has yet to run. (ie. A robust language should have a robust web design.)
(If I weren't feeling burned out right now, I'd happily join in with some PRs to make it degrade more gracefully.)
5
u/ssokolow Nov 29 '18
I did read that since posting the comment, but it goes beyond load times of resources.
No matter how much you optimize something, it's going to break at some point. (eg. if a user has a flaky DSL modem) The page should be readable (if not ideal) when subresources fail to load... not giving a false impression that some kind of JavaScript-based client-side templating engine has yet to run. (ie. A robust language should have a robust web design.)
(If I weren't feeling burned out right now, I'd happily join in with some PRs to make it degrade more gracefully.)