It's Time for Server-Side Browsers
11–20 of 45 posts
Re: It's Time for Server-Side Browsers
#12sorry, I believe this was done ages ago - the remote desktop, such as VNC.
Way before that — the X window system.
He's talking about it working at the same level as a browser where it sees if you have HTML5, and if not falls back to flash, dynamically.
I can't imagine it being a high priority - fiddly, low return, creates huge performance issues. Lots of basic problems - you don't want someone supplying input to a game over a (latent) network. You don't want to be running instances of performance-intensive games on your webserver.
Still - the proposed idea is distinct from VNC or X.
Re: It's Time for Server-Side Browsers
#13Or we could stop treating the HTTP/browser combination as an application delivery platform. It's unpopular here, but it's becoming exceptionally obvious as the correct choice.
Re: It's Time for Server-Side Browsers
#14Could someone translate what this is actually trying to talk about into something clear? This blog post reminds me of someone on weed trying to relate to you this profound idea to you and rambles on stream of consciousness style. He wants there to be no 'centralization' (that is, servers) and have things run on a cloud of people's web browsers, yet at the same time it still talks to mysql somewhere? We won't need any…
You'd get drafted into storing images for some subset of the intersection of your social graph and several others, and the rest of your images would be served by someone(s) with whom your social graph intersects.
Presumably invitations would be via e-mail, or, if you wanted to be even more decentralized, QR code.
Re: It's Time for Server-Side Browsers
#15"I therefore cannot redistribute and decentralise the server-side parts without expecting the end user to understand how to configure and run a server"
You can. It's called a desktop app.
Re: It's Time for Server-Side Browsers
#16Re: It's Time for Server-Side Browsers
#17Re: It's Time for Server-Side Browsers
#18Could someone translate what this is actually trying to talk about into something clear? This blog post reminds me of someone on weed trying to relate to you this profound idea to you and rambles on stream of consciousness style. He wants there to be no 'centralization' (that is, servers) and have things run on a cloud of people's web browsers, yet at the same time it still talks to mysql somewhere? We won't need any…
Presumably he/she envisions a Facebook/BitTorrent hybrid with content replicated across the social graph. You'd get drafted into storing images for some subset of the intersection of your social graph and several others, and the rest of your images would be served by someone(s) with whom your social graph intersects. Presumably invitations would be via e-mail, or, if you wanted to be even more decentralized, QR code.
Re: It's Time for Server-Side Browsers
#19Could someone translate what this is actually trying to talk about into something clear? This blog post reminds me of someone on weed trying to relate to you this profound idea to you and rambles on stream of consciousness style. He wants there to be no 'centralization' (that is, servers) and have things run on a cloud of people's web browsers, yet at the same time it still talks to mysql somewhere? We won't need any…
Presumably he/she envisions a Facebook/BitTorrent hybrid with content replicated across the social graph. You'd get drafted into storing images for some subset of the intersection of your social graph and several others, and the rest of your images would be served by someone(s) with whom your social graph intersects. Presumably invitations would be via e-mail, or, if you wanted to be even more decentralized, QR code.