3 ms·
Personal, and perhaps unkind opinion. This whole paragraph amounts to "it's my site and I can do what I want", which is not a great reason to expect one thing o
by falcolas 7y ago
Personal, and perhaps unkind opinion. This whole paragraph amounts to "it's my site and I can do what I want", which is not a great reason to expect one thing of others, but not yourself.
> First, having a build step creates a dependency on both the build tool and a specific action.
Instead, you push that compute off on your readers; actively harming the environment in the process. Yes, in this day and age I feel it's quite justifiable to point that out. You could render it once and be done with it, but instead you chose to have it be rendered (inefficiently) tens or hundreds of thousands of times, consuming orders of magnitude more energy and generating heat, all to "avoid a dependency". This should be, in this day and age, morally reprehensible.
I'd also point out the irony of the dependency upon javascript for static pages.
> Second, I wanted user interactions within my site to be very fast
A HTML page load from your site with a cold cache 114ms, of which 41ms is connection and TLS overhead, with a fetch time of 70ms. With all of the following requests it's up around 1s before it's rendered (and I'm on a Ryzen-powered gaming computer and fiber). A subsequent fetch of the assets to build one of your other pages is 71 ms (connection re-use means there's no connect time and no TLS time). This time is roughly the same no matter what article or page I pull up.
TL;DR: it's not making your other pages faster. It's just making your first page slower.