Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VNC Viewer for Google Chrome

chrome.google.com

Post reply on HN
Print view View original

21–30 of 57 posts

Re: VNC Viewer for Google Chrome

#23

Post by brittohalloran »

patrickk wrote: post #3

An alternative is Teamviewer- http://www.teamviewer.com/ I've found it excellent. Free for non-commercial use.

Recently switched to join.me and I'm loving it. Easier for the inept person you're helping to get started.

Also, if you're using it for remote presentations, all you do is email a link and they can see your screen directly in the browser.

Re: VNC Viewer for Google Chrome

#26

Post by drzaiusapelord »

mindcrime wrote: post #16

This kind of thing could be interesting. I've often bemoaned the use of HTML/Javascript as a "poor man's X server" and argued that a browser is not necessarily the best way to remote out a UI. VNC, on the other hand, is designed for pushing user interfaces out remotely, so integrating the two could be a very natural step. What'll be interesting to see, is if we can get to a point where there's a very natural handoff…

Why are we still messing around with ancient technology like VNC? Its terrible. It just samples screen output; it does not intelligently understand the underlying GUI so it can't really cache anything or accelerate anything.

If we're going to replace HTML as a "poor man's interface" then we need to do better than VNC. Perhaps NX or RDP.

Still, I'd argue that HTML as a poor man's interface is perfect. I could sit down a write a HTML-based control panel that uses next to no resources. With VNC or whatever, now I need X running on my server, a GUI window manager running, and need to write a desktop app. This isn't progress.

Re: VNC Viewer for Google Chrome

#27

Post by drzaiusapelord »

uptown wrote: post #10
backwardm wrote: post #6

Earlier quoted context omitted.

I use Teamviewer all the time and find it very useful. I need to spend a little time to look at how the connections are made though—I'm not confident that it's secure since you have to enter an ID and password that are (I'm assuming) authenticated by a different machine controlled by Teamviewer. I wonder if the connection is sent through their computers (to get around router issues) and therefore susceptible to captu…

TeamViewer works great - but I share the same concerns. It seems too good to be true, which makes me wonder what I'm sacrificing as a user.

The service itself is an ad for Teamviwer for corporate. The same way join.me is really an ad for Logmein.

Re: VNC Viewer for Google Chrome

#29

Post by mindcrime »

saljam wrote: post #18
mindcrime wrote: post #16

This kind of thing could be interesting. I've often bemoaned the use of HTML/Javascript as a "poor man's X server" and argued that a browser is not necessarily the best way to remote out a UI. VNC, on the other hand, is designed for pushing user interfaces out remotely, so integrating the two could be a very natural step. What'll be interesting to see, is if we can get to a point where there's a very natural handoff…

Well, you can sort of already have that with a bit of JS and NoVNC. http://kanaka.github.com/noVNC/

Oh yeah? Cool, I'll check that out. I hadn't heard of NoVNC before...

Re: VNC Viewer for Google Chrome

#30

Post by mindcrime »

drzaiusapelord wrote: post #26
mindcrime wrote: post #16

This kind of thing could be interesting. I've often bemoaned the use of HTML/Javascript as a "poor man's X server" and argued that a browser is not necessarily the best way to remote out a UI. VNC, on the other hand, is designed for pushing user interfaces out remotely, so integrating the two could be a very natural step. What'll be interesting to see, is if we can get to a point where there's a very natural handoff…

Why are we still messing around with ancient technology like VNC? Its terrible. It just samples screen output; it does not intelligently understand the underlying GUI so it can't really cache anything or accelerate anything. If we're going to replace HTML as a "poor man's interface" then we need to do better than VNC. Perhaps NX or RDP. Still, I'd argue that HTML as a poor man's interface is perfect. I could sit down…

If we're going to replace HTML as a "poor man's interface" then we need to do better than VNC. Perhaps NX or RDP.

Well, I certainly won't argue against that. But at least with VNC it's being used for the purpose it was developed for. Personally I feel like trying to build complex application UIs with HMTL/CSS/Javascript is trying to shoehorn a square peg into a round hole. Browsers are great at, well, browsing hypermedia. I'd like to see that continue and the adoption of something like RDP, NX, or $NOT_INVENTED_YET for remoting interfaces.

Post reply on HN