Cookies do not require javascript, unlike whatever solution using web apis.
At least, that's typically part of how I parse it when people refer to a site as an SPA.
Not just for performance reasons. But because that puts the burden of maintenance of those elements on the website.
It's a lot like how you shouldn't use fixed width and margins for pages. There are a lot of assumptions developers make when building these elements that can easily change and obsolete their work.
So unless you absolutely have to don't take on that burden.
I'm pointing out that a knee-jerk "doesn't work with JS" is irrelevant to 99% of web users.
Be there are other considerations of course, like accessibility, UX consistency, etc (all of which ARE doable in JS if you have to) but that's not what I was responding to, was it?
But that still doesn't mean it's going to be seen by more than either bots or that 1%.
I'm being down voted for pointing out the actual number of users that will care about that effort directly.
HN is hilarious sometimes