fprct

> The only other use case is lots of truly concurrent io within one request/response cycle. But again that is unusual, most apis have low single digit db queries that are usually dependent on one another removing any advantage of async.

Why just "within one cycle"? What about situation where you spend 1s in single db query and are 100ms cpu bound during request handling?

Just imagine a domain from such file being recycled in 10-20 years from now and you building a webpage for the new owner - everything works as expected on dev, stage, test etc - but not on prod when deployed...

Good point.

Would you say that all your "interruption slots" are taken by a need to look at a phone or particular app? Aren't there still situations where you break your current focus (be it something important or just waiting in the elevator) with an actual thought not related to the phone?

I agree that position I've presented probably stands to some degree on the assumption that there still is a noticeable amount of non phone related interruptions of one's thought patterns. Otherwise my claim of equivalence would be stronger and require more arguments that I have at the moment.

From my personal experience (n=1) it's exactly the case - sometimes it's a phone, sometimes not, so that clearly directs my judgement. OTOH I find it unlikely that this is particularly atypical.

It's not really about the smartphones, I think. They are just a symptom of much more fundamental behavior (which may or may not be problematic - depending on how you look at it).

All those 5-10 second breaks -- waiting for a light, waiting for an elevator... If it were not for the phone, what would you typically do? Focus on some random thought or two. Then snap out of it and carry on. The fact that now this is often not a random thought but random input from random app doesn't seem to change that much - pattern stayed the same, just now you can see it in other people from the outside, so it seems more profound.

Confusing behavior after clicking on a company name in search results - would expect to go to some place related to the company (details? yc directory page? product page?), but what happens is some kind of search term change.

I've searched for "read" and clicked on "readme" in search results.

EDIT: Now I see what happens - clicking the first search result is behaving in such weird way - clicking results below the first one works as expected.

Could you outline the most important advances from recent years that you see as contributing to the accessibility you are talking about?

sosqueezed.com (available)

Yes, like some small annotation at the bottom. That's the maximum I could imagine.

Yes, some way of remembrance somewhere came to my mind. But ultimately it felt somewhat intrusive to me and not particularly fitting the new character of the site.