3 ms·
It's easy, I think, to forget how bad the basic HTML / CSS / JS behavior is from a modern aesthetics standpoint. So I'm currently maintaining a totally static
by shadowgovt 4y ago
It's easy, I think, to forget how bad the basic HTML / CSS / JS behavior is from a modern aesthetics standpoint.
So I'm currently maintaining a totally static blog I build in Hugo. It's almost nothing but plaintext, one static CSS file, and some images. One time in a hundred, when I select a new story, the lightly-shaded background of the page blanks through white because loading a couple resources takes too long.
For my personal blog, for fun? That's fine. For most corporate sites? Unacceptable. Looks unprofessional. This is 2022; we're not using teletypes and command-lines anymore where the user can feel the individual bytes coming over the wire.
So to prevent just that one visual hiccup, I'd need to do dynamic fetching of page content and a hollow-and-replace of the content div instead of reloading the entire page when the user navigates around, but I also need to support direct navigation to the page loading the full page content, and I need to do this all correctly from Google et. al's point of view so search crawling doesn't break. And at that point? I'm definitely using a framework (probably with both client and server-side components). All because the aesthetic of the end-user has evolved and your page looks unprofessional if it navigates like a traditional '90s-era page.
- umvi 4y ago> It's almost nothing but plaintext, one static CSS file, and some images. One time in a hundred, when I select a new story, the lightly-shaded background of the page blanks through white because loading a couple resources takes too long. That doesn't sound right to me. Why isn't the "one static CSS file" cached? It should load instantly because it's already in your browser and doesn't need to fetch anything. I've created/maintained static sites as well and I've never run into this visual hiccup you are describing.
- shadowgovt 4y agoExcellent point. Upon further investigation, I suspect what I was seeing was that Chrome with the Inspector open was evicting cache aggressively. Closed it up and no longer saw this issue. Definitely worth remembering for the future that the render loop is more complicated than I assumed!
- redeeman 4y ago> For most corporate sites? Unacceptable. im not nessecarily disputing this, but if so, they clearly are stupid, given all the crap they will put up with
- shadowgovt 4y agoYou're underestimating how much money corporations have to throw at problems, as well as the fact that they compete on look-and-feel with other corporations willing to do the same. At their scale, the cost is worth it; it's just business.
- redeeman 4y agoand yet they tolerate total pieces of garbage that loads a gazillion scripts taking an eternity