Edit: I think javascript and dynamic stuff is great to use where it really speeds things up like a comment popup etc. I think of it like seasoning. Use it sparingly to make a site really great in the places that a full page reload would be a bad experience.
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
Comments
I love the Indie Hackers community and mission of the site, but I can't understand why on earth the site is so JavaScript heavy.
Almost everything on that site could be server side and there is no need for a loading screen that takes 2+ seconds to load!
Again, love what they've done, love the community, don't understand the tech choice.
https://www.indiehackers.com
Edit: I think javascript and dynamic stuff is great to use where it really speeds things up like a comment popup etc. I think of it like seasoning. Use it sparingly to make a site really great in the places that a full page reload would be a bad experience.
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?