Notice the dropdown menu when he types in the address: it says "Broadway 2.0".
I just read the post; I didn't watch the video.
Re:Gtk3 on a HTML5 backend
by loewenskind on Wednesday November 24, 2010 @03:16AM
(#1936833)
Why would someone implement such an awful protocol as X11 when they could just directly render. They could make application-level X11 clients for legacy X apps running on some server somewhere if they wish, there's no reason to cripple the whole experience with X11.
It's hard to understand your question because the quality of its writing is as poor as its punctuation. Can you clarify? What do you mean by "directly render", "application-level X11 clients", "they", and "server"?
Perhaps you were suggesting that remotely displaying a window of, say, FrameMaker in your browser would be better done by rasterizing the application window on the same machine where FrameMaker was running, as with Xvnc, only as a browser plugin.
That is indeed a workable and fairly simple solution, but it usually uses a lot more bandwidth on the network and memory on the machine running FrameMaker than just running X11, particularly with LBX or ssh compressing the X11 protocol.
Re:Gtk3 on a HTML5 backend
by loewenskind on Wednesday November 24, 2010 @07:53AM
(#1937185)
The question is pretty straight forward, but where are the punctuation issues? Are expecting more commas?
When asking a question, you should use a question mark. Your last comma should be a colon or semicolon, or even better, you could split the sentence in two.
I find it perfectly readable anyway, but I'm quite sure the comment is technically right.
Re:Gtk3 on a HTML5 backend
by loewenskind on Wednesday November 24, 2010 @01:05PM
(#1938055)
Using a period instead of a question mark is a writing technique to imply that the question isn't really a question (most commonly used to form polite but firm requests). Touchè on the [semi]colon.
Minimizing latency is still very important in mobile, times of network congestion, and the many places around the world that still have slow connections.
HTML also has the benefits that it's indexable and semi-open-source.
So I hope this is not widely adopted, but it would be awesome for porting existing apps and maybe replacing Flash in some instances.
There's a guide to getting it set up still alive at http://www.csn.ul.ie/~caolan/TechTexts/Broadway.html
This was in 1996, in the X11R6.3 release ("Broadway"), the same release they came out with LBX, the low-bandwidth extension to X, so that you could run your X11 apps over a modem with reasonable throughput.
It never got much adoption. I don't really know why. My guess, though, is that it didn't address the real reasons people were moving from X11 to browser apps: server load, security, ease of administration, latency-tolerance, and ease of development.
Today, server load and latency tolerance are a lot less important than they were in 1996, because computers are a hundred times faster and hundreds of millions of people have ping times under 20 milliseconds, ten times faster than you'd get on a modem.
But security, ease of administration, and ease of development are a lot more important now than they were in 1996.
So, I suspect this won't get widely adopted, but it could go either way. I hope it does!