@nprofile1q... Da lohnt es sich auf jeden Fall zehntausende Mitarbeitende zu entlassen! /s

@nprofile1q... Thanks for the suggestion. I think though, that it is way to JS heavy for me. I want basically everything static pages and I don't need anything like live chat and stuff. Based on NodeJS makes me feel like it might be a resource hog on a small server and with all the supply chain dramas happening in the JS ecosystem, I am not sure I want to run it on my server.

Maybe I should have stated my goals a bit more precisely in my OP.

@nprofile1q... I played both, but actually never finished the second. I remember it being quite a bit more difficult (friggin' headcrabs!), while I finished the first one many times. I remember one run, where I simply did not know how to go further, because there was a wall, that was too high to jump over, but seemingly no other way to continue. But after that run, I never got that far again.

@npub1nqp93... That's actually a good point. We should more often try with an older device. I personally have an X200, so pretty old, but I also don't allow much JS to run with that machine, since it is my free-software-only machine. I guess I also often self-select myself out of visiting bloated websites. But the point still stands for normal people, who want to browse the web with all its stuff. I am not so sure though, that excessive CSS is to blame. I think more often JS is to blame.

@npub1nqp93... For a long time I have not had a situation, in which I crafted some CSS, that made a website slow. Actually it is pretty amazing, how fast modern browser rendering engines are. Websites with sane CSS will not face this issue, is what I think. Of course, we live with a web, in which sane CSS is an exception, not the rule.