3 ms·
Mighty will definitely help with network speed. If your link is Max 60 kb per second download and mighty has a 50 megabytes per second download and it's closer
by graderjs 6y ago
Mighty will definitely help with network speed. If your link is Max 60 kb per second download and mighty has a 50 megabytes per second download and it's closer to the peers for those sites you visit it's definitely going to load faster and then stream down to you.
I haven't used mighty but I'm basing that on my own experience with similar technology.
I think there's a window of optimal use bracketed by low and high download bandwidth for you. if you're faster than that maybe the only speed up you get is if your machine has a slow CPU. If you're slower than that I suspect that the video streaming they're going to use will produce a lag that will make your experience worse than if you were just loading the site directly.
If mighty wanted to push that lower bound lower, instead of streaming video they might be able to stream changes to the DOM. they could compile a sort of single file version of the page on their server that included all the requests the third party resources and styles in line and then whenever there were changes in the layout we could stream those style or DOM changes down to you. As far as I can tell that's basically the minimum amount of information you need to replicate the experience. that might even help a little bit with machines with slow CPUs I sort of tree shaking styles and resources that are not used.
from this point of view with enough development mighty could be purchased by Google as a sort of deluxe subscription model for chrome with bundled premium subscriptions to various streaming services and so on. From that point of view, the bundling up of content, delivery and medium is not really a novel thing because I think similar things have happened with cable TV magazines and news to some extent.
But for the good point that you make that people at the slow or low speck ends might often not be able to afford that kind of service, that lowest of the low-end might be a real focused niche... say people on airplane Wi-Fi or in remote locations on a satellite link.
but from a purely product marketing and psychological point of view I don't think that a product needs actual technical superiority or real measurable utility to become a big hit. I think it really only needs something that makes people want to use it. mighty could position itself as a sort of luxury upgrade for people with already good specs.
Because from the point of view people who are perhaps already of that successful and wealthy mindset many of them may consider that time is their most valuable asset and the accumulated frustrations and annoyance of waiting for websites to load is something they are prepared to pay a service to get rid of and to provide them and experience which they feel is more in line with their station and their expectations of Life in general.
- shp0ngle 6y agoBut you cannot really stream remote browser screen on a 60kvps download.... they recommend on their website that you need 500 mbps or something crazy like that for a low lag.
- graderjs 6y agoSir I disagree. I've gotten away with streaming compressed webp frames of a moderately sized laptop viewport where each frame is between 10 to 34 KB, at a relatively respectable two frames per second. I'm not really joking it's still usable. You can push the frame rate even higher if you're prepared to accept higher compression or lower resolution.
- deleted 6y ago[deleted]
- w0utert 6y agoTwo whole frames per second... Not sure if serious :-/ Two fps at 34KB each is ~500kbps by the way, not 60 kbps
- graderjs 6y agoYep I clearly meant 60KBps not bps :) > Not sure if serious :-/ And I said not really joking so I guess you don't want to believe me XD
- w0utert 6y agoOh I believe you can ‘stream’ stuff at 2 fps over a 500 kbps line alright, the ‘not serious’ part is how anyone could find that acceptable. Even if all you have is 500 kbps... If you would use your 2fps streaming browser to read, say, hacker news, every scroll operation would be hideously slow and pull in another ~60KB per second, even though the page data itself is only a few KB and never changes. Your ‘streaming solution’ only makes sense if the total amount of data to fetch for the page itself outweighs the total amount of data for all the frames you need to stream while you are using the page. Which is probably almost never, unless you always look at static single-page applications which continuously pull in data on the backend without presenting anything new at the front end. Highly unlikely.