3 ms·
This seems like a pretty good example of perfect being the enemy of good. Would there be that much of a usability conflict if /?page=2 30 minutes ago was slight
by rtpg 12y ago
This seems like a pretty good example of perfect being the enemy of good. Would there be that much of a usability conflict if /?page=2 30 minutes ago was slightly different than /?page=2 now?
Not to mention that if a scale of time that large has passed, there's a high chance that the closure-style links expire anyways
- EpicEng 12y agoAgreed. I hated the "expired link" issue. It constantly sent me back to the front page. I would much rather see a newer version of page 2 than to be forced back to the beginning (after a backspace and a refresh).
- couchand 12y agoIt sounds like you don't mind the tradeoff made here but you'd like a better failure mode. That's a great point.
- EpicEng 12y agoYes, exactly. I'm fine with an imperfect solution to this problem, but I think that seeing a page N which was not the page N I would have seen had I clicked the link 30 minutes ago is far preferable to getting a silly error and being forced to navigate back to the front page.
- kevin 12y agoIt's not just about story stream, it was also about different users needing to see different things based on settings, permissions and function outside HN...until recently, the software that powered YC and powered HN were the same. Like Dan wrote, "Getting rid of those closures was a pain, and it made the code more complicated." The tradeoff pg made was for a bit of inconvenience in user experience for a much simpler architecture that allowed him to run HN as a side project while also running YC and writing the essays we've come to admire. You might have made a different decision, sure, but I can't say it wasn't the right call for his circumstances.