Browsers barely care what HTTP status code your web pages are served with

Re:Browsers barely care what HTTP status code your web pages... by somat on Friday August 11, 2023 @06:46AM (#37087187)

Related: the boot scroll. most of the time the scroll of boot messages is harmless and when the system fails to boot it is very very useful to see where. yet the design types hated it. and now no desktop orientated OS shows a boot scroll, opting for a near useless spinner instead.

Opinion: I quite like the scroll, I think it comforting to see what the machine is doing. I think this is why sim city put a fake one in their loader(reticulating splines anyone). I wonder if the sim city messages tied into actual load events and could be used by the programmers to debug the loader. I think the later ones were random, but 2000 might of had an order to it.

[ Parent | on HN ]

Re:Browsers barely care what HTTP status code your web pages... by adamsb6 on Friday August 11, 2023 @02:28PM (#37092098)

I like the standard way that most Linux distros do this: default to a pretty loading graphic, but you can hit esc to see the boot scroll.

[ Parent | on HN ]

Re:Browsers barely care what HTTP status code your web pages... by dwaite on Saturday August 12, 2023 @08:12PM (#37105355)

The boot scroll was/is actively harmful in that it requires process-of-elimination troubleshooting to recognize deviations from a "normal" boot process.

The individual subsystems should be able to recognize their correct state and output a clear diagnostic when they are not in that state. I shouldn't have to step back through e.g. several broken services to find out my second ethernet port didn't initialize.

[ Parent | on HN ]