2 ms·

Granted. It is, however, the worst case scenario as quoted from a marketing piece that's going to render itself in the best light. According to DDG the average

by Kass-y 4y ago

Granted. It is, however, the worst case scenario as quoted from a marketing piece that's going to render itself in the best light. According to DDG the average time for a blink is between 100-400 ms. Okay, maybe they blinked a few times. You're taking on a large complexity problem for the difference between one and a few blinks - and that's in the worst case scenario, which for most applications can probably be ameliorated with pre-loading assets. I'm just not seeing the user-value here. At least not compared to the investment required to adopt more complex architecture and the problems that involves - if your IO really does occur on those sorts of timeframes, (e.g. if you're doing meaningful things at sub 900ms, how are you dealing with race conditions in this distributed architecture? If you're not dealing with race conditions, and have an effectively static set of data that you're just pushing, why aren't you dealing with that via pre-loading the assets?) That stuff's gotta be paid for. Do you think the difference between one blink or... I dunno, let's be generous and say four - I think if I blinked four times it might take longer than a second, mostly due to the delay between blinks - constitutes a competitive edge sufficient to offset the cost?

presentation 4y ago
I’m not arguing that edge computing (vs more tried and true approaches like regional replication) is the way to go per se, but if every action you’re taking on a site with a significant amount of interactivity takes a second, it will feel fairly sluggish; and if your internet connection sucks then it could feel even worse. For some apps that matters, for others it doesn’t. There are other ways to achieve snappiness even with sluggish network conditions, like optimistic UI, but those come with significant complexity too. But yeah if your site doesn’t need it then don’t do it.

by Kass-y 4y ago

presentation 4y ago

I’m not arguing that edge computing (vs more tried and true approaches like regional replication) is the way to go per se, but if every action you’re taking on a site with a significant amount of interactivity takes a second, it will feel fairly sluggish; and if your internet connection sucks then it could feel even worse. For some apps that matters, for others it doesn’t. There are other ways to achieve snappiness even with sluggish network conditions, like optimistic UI, but those come with significant complexity too. But yeah if your site doesn’t need it then don’t do it.