Live data from Hacker News

What the f*** is the edge?

arcentry.com

91–100 of 188 posts

Re: What the f*** is the edge?

#94

Earlier quoted context omitted.

Thanks for the hint, will do (seems to be iOS specific, hmm)

Please just remove anything that interferes with the scrolling at all.

Should be fixed now (there's nothing trying to interfere with the scrolling, just an overflow setting to hide the hamburger menu that seemed to cause the laggy scroll on iOS. (Hopefully I didn't make it worse - redeploying while being Hackernews #1 is always a bit scary)

Re: What the f*** is the edge?

#96

Earlier quoted context omitted.

It's fine if you are going to have your cars remotely controlled with a latency > 150 ms while they operate autonomously as things happen in a shorter time frame. But the other way around seems insane. It's reminiscent of the way people have switched from "human drives, computer deals with emergencies" to "computer drives, human deals with emergencies" as though it was no big difference.

150ms is no big deal. That's on par with top-notch human reaction time. The big deal is the lack of reliability on that connection.

I would equate "lack of reliability" with "latency that is sometimes rather large".

Re: What the f*** is the edge?

#98
post #85
post #82

Earlier quoted context omitted.

It doesn't necessarily have to be due to an ill-decision; thick/thin client cycling can be seen as the obvious result of network/compute cost effectiveness ration swapping. When network is cheaper, thin clients make more sense; when compute is cheaper, then it makes more sense to have it local, and thus thick clients. And due to diminishing returns + economies of the scale, as the market starts investing in one, the…

You may be right, but I'm wary of the implication that 'the market' is rational. Also, if the market leans more towards network or compute (I'm not sure that's a useful distinction, but I'll run with it for now) wouldn't the economies of scale necessarily continue to accentuate the initial trend, rather than induce an oscillating pattern?

Data likes to accrete, almost as if it has its own virtual gravity.

Cycles oscillate some, depending on compute speed and network latency.

But there isn’t as much oscillation as people think. 80’s/90’s style non-networked personal computing was a rare exception to the usual rule of networked centralisation with smrt-ish terminal access.

Re: What the f*** is the edge?

#99
> Cynics might of course argue that we have come full circle, from thick client to butt back to thick client, but that would miss the point of what "the edge" is all about: In a world of increasingly ubiquitous computing power we are well advised to reflect on where our computation happens and how we can make the most efficient use of the resources at our disposal.

Which is exactly why we the cynics say we've come full circle.

Also, while the cyclical nature of client/server design seems to be a thing, unfortunately underlying ownership is not cyclical. For instance, a cycle or two ago, the "edge" computer meant software I bought running on my machine. This cycle, it means software I don't have any stake in running on machine I lease and have little control about.

This is the part of the trend that's worrying to me. Cycles of thin/thick clients are irrelevant. Disenfranchising end users is a problem.

Re: What the f*** is the edge?

#100

> Cynics might of course argue that we have come full circle, from thick client to butt back to thick client, but that would miss the point of what "the edge" is all about: In a world of increasingly ubiquitous computing power we are well advised to reflect on where our computation happens and how we can make the most efficient use of the resources at our disposal. Which is exactly why we the cynics say we've come fu…

> from thick client to butt back to thick client - did you build something that replaces "cloud" with "butt"?
Post reply on HN