7 ms·
This just reminds me how much of a shame it is that the best option for a remote UI today is a localized browser, and the tools that go with it... Don't get me
by tracker1 11y ago
This just reminds me how much of a shame it is that the best option for a remote UI today is a localized browser, and the tools that go with it... Don't get me wrong, I think the browser/web is a great platform, and better than many other options that have come and gone, that said...
It sucks that VNC, X11, and RDP are the best we have... though, I will admit RDP is pretty serviceable, X11 just seems too janky to work over a really remote connection... and VNC, well it works, but, sigh...
I don't think that any remote application UI will really take over as everyone that might work on such a thing wants to gain a lock in with the goal of financial gain... so nothing really reaches a significant market share. This is the case were something that is great and libre/opensource would be better than a standard.
- twsted 11y ago> X11 just seems too janky to work over a really remote connection. Surely It is. But I cannot forget how magic it seemed in the 80s doing titan$ export DISPLAY=zeus:0.0; xeyes & over slow serial lines.
- arethuza 11y agoI cringe to think that I used to use xhost to allow access from any client - don't think there were many firewalls on JANET so anybody could have been connecting to the Sun (later DEC Alpha) I used.
- pantulis 11y agoAnd the next thing would be something like zeus$ xhost + ;)
- gpvos 11y agoxmeltdown
- DonHopkins 11y agoJeremy Huxtable made the original "Big Brother" NeWS version of eyes [1], which inspired xeyes at SIGGRAPH '88 [2], and he also made the NeWS version of melt [3], in just 30 lines of code! My favorite OpenWindows demo was Pat Lashley's monaeyes [4], of course. And I made a fancy version of eyeball windows for The NeWS Toolkit [5] to show off its drag-n-drop and nested window management capabilities, where the eyeball was the window frame, and the iris was the client window, and you could split them in two, and even drag and drop eyes inside of each other, so that sub-eye window frame was reparented inside the moving super-eye client iris! The effect was very creepy and CPU intensive, and I could never quite talk the OPEN LOOK folks into adopting them into the standard. [1] http://donhopkins.com/home/archive/news-tape/fun/eye/eye.ps.txt http://donhopkins.com/home/archive/news-tape/fun/eye/eye.ps.... [2] http://www.x.org/archive/X11R7.5/doc/man/man1/xeyes.1.html http://www.x.org/archive/X11R7.5/doc/man/man1/xeyes.1.html [3] http://donhopkins.com/home/archive/news-tape/fun/melt/melt.ps.txt http://donhopkins.com/home/archive/news-tape/fun/melt/melt.p... [4] http://donhopkins.com/home/archive/NeWS/monaeyes.txt http://donhopkins.com/home/archive/NeWS/monaeyes.txt [5] http://donhopkins.com/home/archive/NeWS/eyes.ps.txt http://donhopkins.com/home/archive/NeWS/eyes.ps.txt
- kjs3 11y agoI ran X over a 128Kbps ISDN line for years. I thought it was pretty usable, as long as you were a bit careful about what you ran over it. XTerms were fine; things like Framemaker were painful.
- tracker1 11y agoAgreed, and in the days of simpler apps, and 800x600/1024x768 displays being more usual, not as bad. I really do miss a lot of this. I mean, the web is great for a lot of stuff (as I said)... but I feel it is a shame that we don't have a modern alternative for client/server applications... and every time I see one that has a lot of potential, it usually has some strings that will prevent adoption.
- creshal 11y agoRDP is the best we have… and at the same time one of the worst kitchen sink protocols I've seen. • Encryption can be completely disabled, forcing plaintext login – to comply with French government orders at some point in the 90s. It's still implemented in a lot of clients, because why not? • Serial and parallel port forwarding (suddenly, USB over JS doesn't seem that surprising any more…) • SMB share forwarding (complete with 8-byte-name-limit) • SMB printer forwarding (as opposed to parallel port printer forwarding). rdesktop's manpage helpfully states that "Keep in mind that you need a 100% match in the server environment, or the driver will fail." Charming! • PCI device forwarding. Holy mother of DMA attacks! You know, WebRTC doesn't seem too bad…
- pjc50 11y agoPCI device forwarding. Holy mother of DMA attacks! Could you give me a citation for this please? Google is unhelpful and only refers to "PCI compliance" which is not at all the same thing (and also a problem for different reasons).
- Zardoz84 11y agoThe last time that I used XN (X11 + deltas + intelligent cache + other extras) worked pretty well on remote. Even works fine over ADSL of 1MB .
- fulafel 11y agoThere's the question of cause and effect in the gradual degradation of the remote X11 experience. A lot of it depends on how the X client is written and pays attention to protocol round trips. In the old days people complained and filed bugs on apps if there was a slowdown in remote X11 performance because many people routinely ran heavy X11 apps on beefy servers and displayed on a wimpy machine. RDP and VNC are immune to this because they are just glorified animated gif streams, but NeWS would be prone to the same problem if it was alive today.
- digi_owl 11y agoShit hit the X11 fan as the DEs adopted OpenGL as an UI accelerator, effectively bypassing X for most tasks. CADT at work yet again it seems, as it the code could iterate faster if they were not bound by having the OGL traffic go through the X infrastructure. From there is has been a hop skip to Wayland, where X is seen as a slowly withering appendage.
- datenwolf 11y ago> Shit hit the X11 fan as the DEs adopted OpenGL as an UI accelerator, effectively bypassing X for most tasks. That's not correct. If DEs actually were using OpenGL for UI acceleration, then at least for GL-2.1 and earlier everything would be sent as pure drawing commands to the display server by means of the X11/GLX transport protocol (indirect rendering context). What actually happened was, that for some reason the developers of the toolkits thought, that it was somehow necessary to render everything in the client into a pixmap and only as a last step pass this through the X11 to the graphics hardware, thereby degrading the X11 server to a glorified bit-blitting machine. That's why the design of Wayland is how it is, because toolkits developers couldn't be bothered to actually using the X11 drawing primitives in a clever way. And if you're not a total moron you can make it look extremely good. One thing that I never understood is, why antialiasing was never enabled for X core drawing primitives; it's not like you couldn't use raster ops with antialiased geometry either (like the XOR overdraw method).
- digi_owl 11y ago
- theoh 11y agoIsn't it essentially possible for anyone with the equivalent of shell access on a remote machine to implement a system like Rob Pike's Sam editor? You can roll your own economical protocol, which could include mobile code fragments (regexps sent to remote process for execution, for starters). I'm not sure why you think we're stuck with the browser for this, or if that's a bad thing for most applications that don't involve something bandwidth-intensive like realtime 3D. "Sam is implemented as two processes connected by a low-bandwidth stream, one process handling the display and the other the editing algorithms. Therefore it can run with the display process in a bitmap terminal and the editor on a local host, with both processes on a bitmap-equipped host, or with the display process in the terminal and the editor in a remote host. By suppressing the display process, it can even run without a bitmap terminal." http://doc.cat-v.org/plan_9/4th_edition/papers/sam/ http://doc.cat-v.org/plan_9/4th_edition/papers/sam/
- mcguire 11y ago"You can roll your own economical protocol..." Aye, and there's the rub.
- 0xdeadbeefbabe 11y agoI don't know: "I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones. This has been brewing since april, and is starting to get ready. I’d like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things)." -http://www.thelinuxdaily.com/2010/04/the-first-linux-announcement-from-linus-torvalds/ http://www.thelinuxdaily.com/2010/04/the-first-linux-announc...
- theoh 11y agoMaybe so. Actually I think maybe the way you factor the application may be more crucial. I love the story about MVC being invented in the context of shipbuilding, because it's such a heavy duty business, and obviously the view (drawings) and the model (the state of steel fabrications under construction) have such totally different characteristics with respect to changes.
- e40 11y agothough, I will admit RDP is pretty serviceable, X11 just seems too janky to work over a really remote connection... and VNC, well it works, but, sigh... I used, every single day, a product called "FastX" from StarNet, that runs X over RDP. It means the X programs I display on my Mac (which are running on a Linux box) are disconnectable/reconnectable. I disconnect when I'm ready to go to work, reconnect there, and do the same thing when I finish at the end of the day. Absolutely lovely.
- tracker1 11y agoAgain, commercial product, low-end/individual pricing doesn't seem to be listed... There have been a few similar products about a faster remote experience with linux. I've tried a couple, but the commercial bit always rubbed me a little bit... I mean, if the pricing is open for personal use, and reasonably priced, I'm all in. That hasn't been the case in my experience.. thanks for the heads up though. I tried NoMachine's NX for a while, which was very nice.
- tracker1 11y agoOkay, looks like NoMachine is now free for desktop/personal use all around... didn't use to be the case (outside linux version)... May have to give it another look.