They know ssr is a thing which is why they used that term. But ssr produces a static page or static component, where webapps often require some level of interactivity for their basic functionality, such as reacting to server events. They're asking if that can be achieved with ssr
PeriodicallyPedantic
Maybe I'm out of the loop because I do mostly backend, but how do you update the chat window when new chats come in, without JavaScript?
Back in the day people be naming birds like "brown tittied groundling gayfa**ot" and nobody be batting an eye
I can also behave _my_self
Fucking CERN needs to hire this man, he created an entire sun in his kitchen. They've been trying to contain nuclear fusion for decades and my man does it by accident in a pastry.
They should be. But they aren't.
Which is especially egregious with the terrible investment in public transportation. You want poor people to stop speeding? Give them a decent alternative to cars.
Flat fines mean it's only a crime for the poor
God that reminds me of the end of this "Good Luck, Babe" parody
(Sorry its tiktok, I couldn't find it anywhere else but Instagram)
If you have enough experience to make your own custom adventure for your players, I'd recommend that, so that you can easily adjust it to suit your players needs and preferences, as you go.
But if if you're not comfortable with that, then probably just use the campaign that comes with the d&d starter pack (lost mines of phandelver or something like that).
It's not an especially amazing campaign, but it has a decent mixture of dungeon crawling and roleplaying, and the story/encounters are simple enough for beginners to understand. It's a safe bet to ease players into TTRPG.
You could also try a totally different system. I hear good things about Blades in the Dark. I've never played it, but what I hear sounds like it avoids overwhelming new players.
Elevators exist to give enough time to load in the next floor.
Naw dog
He's an emo hedgehog
I also feel like everyone seems to be missing that we're taking about degradation, which isn't usually "no js at all", it's some subset that isn't supported. People use feature detection to find out of some feature is supported in the browser and if it's not the they don't enable the feature the depends on it.
For the chat example, you could argue that a chat can degrade into a bulletin board, but I'd argue that people use chat for realtime messaging so js is needed for the base use case.
If your webpage primarily just displays static information, then I agree that it should work without js or css. Like Wikipedia, or a blog, or news, or a product marketing page, or a forum/BBS.
But there is a huge part of the web that this simply doesn't apply to, and it's not realistic to have them put in huge effort to support what can only be a broken experience for a fraction of a percent of users.