Comment on The boring front-end developer (2014)parentComments−jb36897yYeah, in my ETL work we call things like this bugs. I've never understood why this is acceptable on the front-end. Users seem to have been conditioned over the years that it's just "slow internet" I think and are willing to wait for an app to load−jv222227yYeah. And how much code has to load?Given that I can get 100k image in a few seconds!!! Ie Why would it ever need more than 100k JS after compression and thus < 1s to load?Even if it is a big size why not cache and be instant on load?If the answer is it needs to use Ajax to load data after loading the js, then why not include that data on initial load?
Comments
Yeah, in my ETL work we call things like this bugs. I've never understood why this is acceptable on the front-end. Users seem to have been conditioned over the years that it's just "slow internet" I think and are willing to wait for an app to load
Yeah. And how much code has to load?
Given that I can get 100k image in a few seconds!!! Ie Why would it ever need more than 100k JS after compression and thus < 1s to load?
Even if it is a big size why not cache and be instant on load?
If the answer is it needs to use Ajax to load data after loading the js, then why not include that data on initial load?