What's funny is that Discourse serves static HTML and I can view it with JS disabled. Why even add this stupid splash screen that blocks the view?

@volpeon I think we read a thing once that said Google had a bullshit metric that praised your site if it changed as much of the screen as possible at the earliest opportunity ("largest contentful paint" or something), and that's why those splash screens are /everywhere/ on the internet now.

So I'd say blame both Google for the metric and the forum software devs for trying to optimize for it at the expense of usability.

@volpeon even with javascript that splash scrrrn is annoying

@volpeon pretty sure the static HTML version is extremely bare-bones, the actual UI is entirely client-side JS

@lambda Sure, but what's stopping them from showing the static UI and instantly replacing it with the JS version once that's ready? Why assume the JS will work when it isn't loaded yewt and make the static UI unusable with a splash screen?

@tay I have never encountered a website that made me go "thank god this splash screen was there or I would've left instantly" — more like the contrary. ​​

@volpeon probably the fact that the JS takes several seconds to load on a good day, which would change the entire UI when the user is already in the middle of using it

@lambda It's almost as if other forum softwares which deliver a full-featured static version and only use JS to improve the usability found the better solution to this problem