7 ms·

I love that 1996 HTML solved deep linking. It works flawlessly: https://www.spacejam.com/cmp/lineup/quiz1a.html https://www.spacejam.com/cmp/lineup/quiz1a.html

I love that 1996 HTML solved deep linking. It works flawlessly: https://www.spacejam.com/cmp/lineup/quiz1a.html https://www.spacejam.com/cmp/lineup/quiz1a.html Look, I just linked to a wrong answer the middle of a quiz. It perfectly preserved all the state. (Fun quiz, too.) This is mostly a tongue in cheek argument, but it has the benefit of being true. Sadly the quiz seems broken at question 6. But you can even un-break the quiz by manually editing the URL to question 7: https://www.spacejam.com/cmp/lineup/quiz7.html https://www.spacejam.com/cmp/lineup/quiz7.html Imagine trying to do that with a React app. (And I say that as a fan of react apps.) The ending of the quiz is hilarious, by the way.

onion2k 6y ago
Imagine trying to do that with a React app. It'd work fine if the developer used the URL to maintain state with React Router's BrowserRouter or HashRouter.
- recursive 6y ago
  In other words, not by default.
  - onion2k 6y ago
    No, but even back in 1996 you didn't have to use the URL to store the state of a user's game. They could have used a cookie (supported in Mosaic since around 1994), or used a server-side session (I think was cgi::session a thing back then). That was a technical decision someone made. Those sorts of choices when you're speccing a web app haven't changed. These days it would be a bit unusual to use routing to store the game state admittedly but that's why it's good to have older devs like 43-year-old me on the team. I actually think about these sorts of details rather than using the defaults. It's also worth noting that storing the state in the URL shouldn't be the default. Being able to see the state by reading the address bar would be a security issue for most apps.
    - rbanffy 6y ago
      The elegance of using a static URL is that you are not really keeping the state - you instantiate all possible states and let the user traverse them according to whatever state they happen to be in (and able to see). There is no spoon.
- GrumpyNl 6y ago
  All thats wrong with the modern web is in this answer.
  - onion2k 6y ago
    Probably 3/4s of the people who post on HN can attribute their entire career existing to "the modern web", so maybe there's some good things as well as bad things about it.
    - rbanffy 6y ago
      I believe some of the conceptual simplicity of the "olden web" is missing in the age of leftpad.
    - minimuffins 6y ago
      "My career exists because of it" isn't a great argument for its actual merit.
5Qn8mNbc2FNCiVV 6y ago
Nextjs wants to talk with you xd
vesche 6y ago
I like how you can tell that the HTML was done by hand. There's a parallel here, something like: handmade furniture is to hand written html as mass produced furniture is to generated html. There's a quality to it.

onion2k 6y ago

Imagine trying to do that with a React app. It'd work fine if the developer used the URL to maintain state with React Router's BrowserRouter or HashRouter.

recursive 6y ago
In other words, not by default.
- onion2k 6y ago
  No, but even back in 1996 you didn't have to use the URL to store the state of a user's game. They could have used a cookie (supported in Mosaic since around 1994), or used a server-side session (I think was cgi::session a thing back then). That was a technical decision someone made. Those sorts of choices when you're speccing a web app haven't changed. These days it would be a bit unusual to use routing to store the game state admittedly but that's why it's good to have older devs like 43-year-old me on the team. I actually think about these sorts of details rather than using the defaults. It's also worth noting that storing the state in the URL shouldn't be the default. Being able to see the state by reading the address bar would be a security issue for most apps.
  - rbanffy 6y ago
    The elegance of using a static URL is that you are not really keeping the state - you instantiate all possible states and let the user traverse them according to whatever state they happen to be in (and able to see). There is no spoon.
GrumpyNl 6y ago
All thats wrong with the modern web is in this answer.
- onion2k 6y ago
  Probably 3/4s of the people who post on HN can attribute their entire career existing to "the modern web", so maybe there's some good things as well as bad things about it.
  - rbanffy 6y ago
    I believe some of the conceptual simplicity of the "olden web" is missing in the age of leftpad.
  - minimuffins 6y ago
    "My career exists because of it" isn't a great argument for its actual merit.

5Qn8mNbc2FNCiVV 6y ago

Nextjs wants to talk with you xd

vesche 6y ago

I like how you can tell that the HTML was done by hand. There's a parallel here, something like: handmade furniture is to hand written html as mass produced furniture is to generated html. There's a quality to it.