Google Releases Open Source NX Server 257
wisesifu writes with news of a new open source NX server, dubbed NeatX, that was released by Google and promptly lost in the shuffle of the Chrome OS announcement. "NX technology was developed by NoMachine to handle remote X Window connections and make a graphical desktop display usable over the Internet. By its own admission, Google has been looking at remote desktop technologies for 'quite a while' and decided to develop Neatx as existing NX server products are either proprietary or difficult to maintain. 'The good old X Window system can be used over the network, but it has issues with network latency and bandwidth. Neatx remedies some of these issues,' Google engineers wrote on the company's open source blog. NoMachine had released parts of the source code to its NX product under the GPL, but the NX server remained proprietary. [...] Neatx is written in Python, with a few wrapper scripts in Bash and one program written in C 'for performance reasons.'"
Sucks to be NoMachine (Score:5, Funny)
Poor NoMachine... now they don't have a product
Re: (Score:2, Interesting)
You mean NoProduct(TM)
Re:Sucks to be NoMachine (Score:5, Funny)
Poor NoMachine... now they don't have NoProduct
Fixed that for 'ya.
Re:Sucks to be NoMachine (Score:5, Insightful)
FreeNX has been around for quite some time and that hasn't killed NoMachine off. However, Google being involved may create more OpenSource developer interest in NX and perhaps someone will create a good Windows NX Server, Windows NX Client and better management tools. If Google rallies that much developer support it could mean an end to NoMachine.
Re:Sucks to be NoMachine (Score:4, Interesting)
Re: (Score:3, Insightful)
So Google is about to launch a product providing remote desktops, vendors will build thin-terminals around it, and NoMachines has a commercially-available well-tested server ready to sell with support for in-house use of these terminals... I think they'll be OK, once the corks stop popping.
FreeNX (Score:2)
Was ( is ) open source i thought.. Either way, another player isn't a bad thing. Especially if its painless to setup on FreeBSD.
Re:FreeNX (Score:5, Informative)
It's mentioned in the article. It says that Google rejected it because it's a mess of Bash, Expect, and C and very hard to maintain. Their implementation is mostly Python, with a little C and Bash.
Re:FreeNX (Score:4, Funny)
Re: (Score:3, Funny)
"It says that Google rejected it because it's a mess of Bash, Expect, and C and very hard to maintain. Their implementation is mostly Python, with a little C and Bash."
I would certainly expect some serious C bashing from a Python-using company. Or did I just C them bash expect?
Re: (Score:3, Funny)
Wow, won't Google look silly now that you've told them that X11 exists! I bet they never even realized!
Re: (Score:2)
In fact it is quite possible that they never did.
Re:FreeNX (Score:5, Funny)
Couldn't they just google it?
Re:FreeNX (Score:5, Informative)
They are not reimplementing it, they are providing a wrapper to the X11 protocol so it performs better on low bandwidth, high latency links.
Ever tried do to remote X over, say, a 2Mb/s connection? Try it again with FreeNX and notice the large improvement in display performance.
Now if only they would somehow include GL in remote X.
Re: (Score:2)
> Now if only they would somehow include GL in remote X.
That's what xgl is.
Re: (Score:2)
Would that use the local video card for acceleration? What I would like is a solution that would allow me to connect to a remote KDE session and have compiz-fusion work over the NX connection. At the moment if compiz is enables on the server, it is not used in the NXClient end, even if the client desktop has compiz enabled too.
Re: (Score:2)
Ever try remote X over, say a *slow* connection. 2Mb/s is not slow. But I started when 10baseT was the norm and sometimes ran X over a 28.8 or 14.4 modem.....
Re: (Score:2)
Were you using a desktop with as much eye candy and visual features as is available today?
Re: (Score:2)
Ever tried do to remote X over, say, a 2Mb/s connection?
While one can't deny the value of a compressed X protocol, a lot of the performance issues come from the modern toolkits that are heavily dependent on pixmaps for drawing everything. Athena, Tk, WxWidgits (in native mode), Motif, and Openlook all run pretty decently on a 2Mbit link. It's just when you throw GTK+ (especially Gnome apps) and KDE into the picture that the old-protocol-that-could gets bogged down.
Re: (Score:2)
I've done X over a 28.8k modem. It was ugly.
Moving to 128kbps ISDN made things hugely better. Using SSH compression was better still. And differential X [vigor.nu] was fairly usable with lots of X11 software at the time.
But in reading this announcement, I can't help but think: Isn't this the same as Broadway [faqs.org]? It seems that it was released [opengroup.org] along with X11R6.3, which Wikipedia says went public on December 23, 1996. Wikipedia's article on XFree86 also implies that it should've been in the hands of Linux users someti
Re: (Score:3, Informative)
Except that NX is neither a full re-implemetation of X11, nor is it done badly. Instead, it actually works over very slow links.
Re: (Score:3, Informative)
And it works quite well. Around here, it is the standard solution when one needs to run engineering applications (on Linux) from home. Our home machines have Windows, but NoMachines has quite a nice NX client for Windows. As far as efficiency and general "snappiness" it comes quite close to Windows Remote Desktop, but works well with a Linux host.
Two thumbs up for Google. Maybe they can fix some of the annoying bugs. The NoMachine NX client does NOT work well with two monitors. They claim that this is
Re: (Score:2)
Re:FreeNX (Score:4, Interesting)
X-protocol SUCKS for low-bandwidth high-latency links.
NX can require 100x less of bandwidth on some tasks. I remember reading news using 19200 modem link other the NX connection.
Re: (Score:2)
Sorry, English is not my native language and it was past the midnight in my timezone.
NX requires much less bandwidth than plain X protocol, it achieves this by caching and compression. Plain X protocol has no compression whatsoever, and piping through a general-purpose compressor does not work well either.
NX caches and compresses streams of commands, so if you open a menu (for example), it will cache the stream of commands and just refer to them in future.
This achieves great levels of compression, so NX can
Re: (Score:2)
"English is not my native language"
My apologies, then sir. I see similar expressions used in advertising all the time. It really is a form of advertiser speech, and it bugs the hell out of me. But, in this case, I am at fault for assuming you are a native English speaker.
Thanks for reposting - it makes perfect sense now. :-)
Re: (Score:2)
No problem!
"I see similar expressions used in advertising all the time." - that's probably why I wrote it, it seemed familiar.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
X is already implemented badly... at least when it comes to running over the Internet. Don't let the fact that you managed to run xeyes once over an SSH connection on your Gigabit LAN fool you into thinking that X will runs well over the Internet, as I can assure you it doesn't. The kicker that drove me over the edge was when I noticed that X was sending a packet over the wire every time the #%@#%@T cursor blinked. I posted it to some forums where there were multiple fingers pointed back & forth betw
Re: (Score:2)
NIH (Score:5, Insightful)
From TFA:
"There is a free implementation of an NX server based on NoMachine's libraries named FreeNX, but this did not appeal to Google.
"FreeNX's primary target is to replace the one closed component and is written in a mix of several thousand lines of Bash, Expect and C, making FreeNX difficult to maintain," according to Google.
Neatx is written in Python, with a few wrapper scripts in Bash and one program written in C "for performance reasons". "
It was unmaintainable because it was written in Bash, Expect, and C, so they rewrote it in Bash, Python, and C?
Re:NIH (Score:5, Funny)
Re:NIH (Score:5, Funny)
Well, they started to rewrite it in a mix of Haskell, Visual Basic, and Perl. But the project managers kept spontaneously combusting, so they had to go for a language combo that was a little more commonplace.
Re: (Score:2)
Re:NIH (Score:4, Insightful)
In other words: Those who do not understand Haskell (which admittedly is hard if your brain is limited to OOP and procedural coding), will re-implement it
This just screams a "fixed that for you" post... I think you mean Lisp, don't you?
Re: (Score:2)
Sir, here's your response:
"You clearly never have seen or understood Haskell. :) One word: Monads."
Want a basket of parentheses with that? [xkcd.com]
Re: (Score:2)
Meh, monads are just trickery to introduce sequencing in a fundamentally declarative language. Nifty, to be certain, but I wouldn't call them all that interesting or revolutionary outside that particular model of computation.
Re:NIH (Score:5, Informative)
Well, it would depend on how much code was written in each language in the original.
NeatX appears to be 90% Python, with only a few stuff in Bash and C, so its basically just a Python app
Re:NIH (Score:4, Informative)
Good question -) However, have a look at the different language breakdowns between the codebases.
FreeNX:
5.4k lines of bash
233 lines of C
102 lines of expect
Neatx:
5.7k lines of python
400 lines of C
54 lines of bash
The bash in neatx is there to provide wrapping of the python code, so that any unhandled errors etc are logged. It's a belt-and-britches approach.
Steve, Neatx project lead
wasnt that the whole point of XWindows? (Score:2)
Re: (Score:2)
Yes. But it failed to account for future advancements in graphics technology. Thus regular desktop usage became too heavyweight for wide deployment. Thin clients splintered in the directions of Citrix, NX, and VNC. Microsoft also screwed over Citrix and developed RDP.
NX basically is the X11 protocol with many of the issues that make it suck removed. This is accomplished through imperceptible delays to bunch up commands, compression of packets, and caching of previously
Re: (Score:2)
Much more of a problem is that the X design assumed latency would be small compared to bandwidth.
Far too many X calls require a value returned by the server, which means two latencies no matter how tiny the messages are.
I suspect most of NX's speedup is due to it emulating a lot of the server on the local end so that a lot of answers are sent back from the local copy. Unfortunately this can't be used for everything, as it will defeat the cooperative nature of X, for instance you can't get an answer that dep
Beats Web-apps (Score:2, Interesting)
Of course the obvious problem with this is finding a way to block the ads running in a remote application. Maybe not if they always appear in the same places, but knowing Google I doubt they will.
Re: (Score:2)
Re: (Score:3, Interesting)
You joke, but between the Canvas [whatwg.org] and Web Socket [w3.org] standards, I don't see any reason why they couldn't.
Granted, WebSockets have yet to be implemented in browsers, but I hear Google owns a fairly popular one...
Re:Beats Web-apps (Score:4, Insightful)
Well this sure beats HTML+HTTP and Javascript for displaying remote applications.
I'm so tired of people comparing web apps and X. They are completely different beasts.
Web apps are downloaded to your local PC and run there. Many web apps make frequent HTTP calls to sync with, or access resources, on the server, but that's completely optional. Web apps are often the right solution compared to X apps because they leverage the power of your local PC. While writing this comment, my local PC did the spell checking, it handled the keyboard events, and it updated the display, all without any communication to, or from, the server. It was fast and responsive and efficient because it all happened entirely on my local PC. The only communication that will occur with the server is when I click on Submit.
In contrast, X apps are run on the server and merely displayed on your local PC. Slashdot could not possibly function that way without enormous hardware and bandwidth upgrades, and even then it would probably be an annoying experience for many users on connections that experience frequent lag.
Web apps and X apps are not really competitors. They serve two different purposes. Web apps leverage the local PC and can also leverage the server where it makes sense. X apps are basically entirely run on the server with only display updates being sent to the client. This setup made sense a long time ago when servers were extremely powerful and client PCs were weak. Now that even modest hardware is extremely powerful, X makes very little sense.
Long time user (Score:5, Interesting)
Re: (Score:2)
Re: (Score:2)
Re:Long time user (Score:4, Informative)
Even DXPC (NX is a fork from that software) kicks VNC's ass.
Re:Long time user (Score:5, Informative)
But what does NX have over VNC?
The performance is an order of magnitude or five better? Honestly, unless you're on something with REALLY high latency, even raw, unmassaged X is frequently better than VNC performance-wise. NX however is hands-down the best performing remote display protocol I've seen. Decently performing (very usable for basic office tasks) full modern desktops when the link has 400ms+ latency and 10kbps bandwidth. It knocks ICA and RDP into a cocked hat.
Re:Long time user (Score:4, Informative)
Re: (Score:2, Interesting)
Re: (Score:3, Interesting)
Re: (Score:2)
"Does it map printers, serial, and USB devices? Does it support drive mapping?"
Yes, as far as I know, all of these are supported.
Re: (Score:2, Interesting)
I think the GP means printer, serial and USB devices at the *client* end. With RDP you can make a printer or drive attached to your local PC accessible to the application running in your server session. Very handy for local stuff.
I don't think NX supports that.
Re:Long time user (Score:4, Informative)
I assure you that I *can* read, and I am sure you can too [nomachine.com]:
Re: (Score:2)
Re: (Score:2)
NX Free edition is non-trivial to install? There are three packages to download and install off of nomachine's website. It just works once they're installed. What are you talking about?
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
I haven't had any trouble installing or maintaining freenx. it was the same as any other package I installed.
what troubles might i have had?
Re: (Score:2, Interesting)
One possibility is if it's taken up by OS vendors (Linux distributions, Apple) as their remote windowing solution. Red Hat/Fedora is heavily VNC-focused -- with the installation process doable over VNC, and both full desktops (GNOME and KDE) coming with their own VNC servers. Apple's OS X also has a VNC server, AFAIR. Microsoft, naturally, has their own solutions...
Google will most likely use this in some way within Chrome OS -- if it shares many innards with Android, the graphics obviously won't be X11-bas
Re: (Score:3, Informative)
I feel like I'm one of a couple dozen NX users
I don't know if many people use NX, but I sure do install it on all my servers now. And while I had trouble with FreeNX, the NoMachine version was really easy to setup [alma.ch].
(I use it with meld and sshfs to compare /etc trees between similar servers.)
Where would such technologies be really useful? (Score:2)
I wonder whether there are environments where technologies like NeatX can be regarded as "God sent" solutions.
I know the technology and have used it several times but I still fail to see how it could be useful given the enormous power today's systems have.
I guess I am calling for serious implementations...anyone?
Re: (Score:2)
Think schools, students and homework. I work in the world of Linux and LTSP in education. LTSP has already given schools the gift of easily maintained, green, FOSS computing. NX would be *perfect* for kids needing access to their desktop from home, for, say, homework. Like telecommuting, but for school. =)
Re: (Score:2)
NX would be *perfect* for kids needing access to their desktop from home, for, say, homework. Like telecommuting, but for school.
Not if the parent doesn't allow the kid to access the Internet for more than the thirty minutes a day in which the parent can directly supervise the kid. Homework often takes longer than that to complete.
Re: (Score:2)
That would be an issue of the household, not the technology. Parents should know if the child is using computers for school. Computers are getting everywhere - that's an old way of thinking about computers (I.E. putting them on the same plane as television or video games).
Re:Where would such technologies be really useful? (Score:5, Informative)
VNC/RDP, for instance, make it really easy to have your entire desktop session, with all open programs, program state, etc. on one computer available over the network from another computer. If you have a whole bunch of windows open, with lots of tabs, and a half finished document, and some other stuff you are referring to, it is way more convenient to just connect to your session, rather than try to recreate it on another machine.
Citrix, X, and NX are really convenient for situations where a program's context matters. If I just want to type out a shopping list, or check a web page, it doesn't really matter where the program I use runs(which usually means that I should run it locally, because latency sucks). If, though, I'm opening my bittorrent client, or trying to edit some documents at work, it matters where the program is running. I want my bittorrent client to be running on a computer with a fast pipe and a big disk, even if I'm controlling it from my cellphone. If I'm trying to edit some work documents, I want Word running on my work's LAN, so all my documents on the fileserver will be available(without the risks involved in just copying stuff to my laptop, then leaving it on the train).
I worked at a school where the latter use was common and fairly highly valued. We didn't want to deal with the hassle of hundreds or thousands of potentially infected machines belonging to students and faculty having VPN access to the LAN. We did want students and faculty to be able to access their documents and email when they were at home. To solve the problem, we used Citrix to offer remote access to all the common programs that students and staff would use to view or edit documents, set up so that the programs would have access to the files of the user that logged in.
It wasn't perfect; but it largely worked. The user would go to a web portal, enter their credentials, and get a bunch of clickable icons. Click on "Word" or whatever and it would(after a few moments of Citrix doing its thing) pop up, looking modestly like a local application. If you hit "Open", though, you'd have access to all your documents from our fileserver. Super easy.
Re: (Score:2)
Re: (Score:2)
NX is great for programmers. When I'm coding, I have 30 emacs windows open, 10 terminals, 50 tabs in Firefox, etc., spread across several virtual desktops. It takes a while to recreate that state, especially when it's not just the windows, but a lot of useful stuff in each one. With NX, I can grab my laptop for a while and within 5 seconds I'm accessing the same desktop, with no perceptible latency. I just need to scroll a bit since I'm viewing a large desktop on a small screen - but it's much better to
Re:Where would such technologies be really useful? (Score:5, Interesting)
Because NX on modern hardware can provide a user experience that is virtually indistinguishable from a local desktop.
Even X or VNC on a fast connection with fast machines on both ends will feel a bit sluggish. NX works great on old hardware with slow connections -- if you've got multiple clients, you can squeeze more clients out of the same hardware/bandwidth. This can be a *huge* deal.
NoMachine's products aren't cheap, but can be totally worth it given the cost savings in hardware, bandwidth, and support. Their free version also works great for anything but a terminal server.
You can chalk me up as a *huge* fan of NX.
NX just got a little better (Score:2, Interesting)
I love FreeNX and have used it for a long time, I can't wait to try this...
I also love Python as a language and I used to be an it's C/C++ or Java or it's not worth it.
After falling in love with Python, it is let me see if python can handle this with speed, if not, I'll write a class in C and use python to Access if needed.
I don't really see why they even really need the bash scripts though.
If you use any POSIX system remotely and like GUI's, NX is a must. VNC and Plain X are slow (even with ssh compressio
Re: (Score:2)
After falling in love with Python, it is let me see if python can handle this with speed, if not, I'll write a class in C and...
You have some serious C skillz.
Re: (Score:2)
I have a feeling you won't be writing a class in C.
Sure, ya can. Create a struct with function pointers. Ta da! Just very little language support for silly things like "inheritance" ... Call it "explicit polymorphism!"
Re: (Score:2)
The whole OO paradigm seems to be founded on the belief that a whole new terminology of classes, objects, inheritance, and polymorphism is less confusing than function pointers.
I'm a python fan, but not for the OO features. I like the dictionaries. Especially when you stuff them full of function pointers.
NX is teh shindiggity! (Score:5, Informative)
It might be worth mentioning to some people who are no doubt confused; there is a difference between FreeNX and NX Free. And on a futher side note, I have tried installing FreeNX two or three times and the packages seemed to be unavailable from distro repo or even from the berlios FS (Weird!). In any case if this Google NX server isn't a piece of junk I will be over the moon!
In my opinion NX is #1 remote display (also sound and printing) technology there is. You get a great quality image over a very slow DSL connection! VNC doesn't come anywhere near it - and for the $0 price tag you can't beat it!
The trouble with NX Free is that it can only allow a few simultaneous connections at a time - I'm hoping Google's server changes this.
Good news well done Google. Another option is xpra (Score:5, Interesting)
This is excellent news, I've really enjoyed using NX but always found it slightly temperamental to use. Still, it gave me high performance rootless application access over a dodgy wifi link in Germany, back to my machine at uni in the UK - with the ability to resume every time the wifi dropped. I've known people have trouble resuming dropped sessions, though it worked when I needed it. Anything which is well-supported and makes NX nicer to work with is very welcome - I hope Google press on with making this better and better. It's be real nice if they'd make an open source client available too, preferably with a choice of front-end widget libraries ;-)
Another project, which I actually head about on Slashdot and am very impressed by is Xpra: http://partiwm.org/wiki/xpra [partiwm.org]
Xpra = X Persistent Remote Applications, i.e. connect to your xpra server (tunnels through ssh by default) to get rootless applications delivered to your desktop, disconnect and reconnect somewhere else and get the same apps back. Like screen, for X. It's not meant for fast-changing displays, e.g. video. But it's a nice, compact approach that largely consists of a few thousand lines of Python. It uses modern X extensions cunningly to get the job done without having to understand most of the X protocol itself. And, somewhat like NX, it's better suited to high latency links than simple X11 protocol is. These days I think Xpra is starting to get more advanced features such as Windows client support, theme matching for remote and local apps, some clipboard sharing, etc. It's a nice little app that has its uses, particularly if you want something simpler than NX to set up and administer. The server can also be easily run by an unprivileged user whereas I'm not sure if that's the case for NX (?).
Re: (Score:2)
Actually, replying to myself: what I'd *really* like to see is some funky modern window manager that leverages X11 extensions in a similar way to Xpra to enable forwarding of apps I started *locally* over some network protocol. Perhaps there's a reason this can't be done but I'm not really sure what it could be? I don't want to have to decide in advance which apps I might want to migrate - and I don't want to suffer performance penalties whilst I'm not remoting them.
Xpra, sadly, can only display apps you
Re: (Score:3, Informative)
Replying here to both your post and the one you replied to:
As I understand it, Xpra's cunning hack is to run a real X server (such as Xvfb, which just "displays" to some memory for debugging purposes - or even Xvnc (!)) somewhere. Then the Xpra server registers itself as a compositing manager (so the complete contents of windows get handed to it for compositing). The server uses XDamage (notification on bits of windows that changed, I think) to get told when some contents change, then reaches into the win
neatx client (Score:3, Interesting)
Re: (Score:3, Informative)
http://blog.gwright.org.uk/articles/2006/08/23/qtnx-ready-for-public-consumption [gwright.org.uk]
From the horse's mouth (Score:5, Informative)
URI scheme name to launch remote apps (Score:2)
before GTK (Score:2)
You could use X over a dial-up connection on Motif or Athena. Of course it's not the bandwidth, it's the latency. And the latency of a 14.4K connection is pretty acceptable if you turn off MNP5 and other compression junk, even though X protocol compresses very well the modems tend to have worse latency with the built-in compression. LBX (low bandwidth X) was usually a better compromise than running the general purpose compression, if you were lucky enough to have hosts with the LBX patches installed.
Low Bandwidth X (Score:2)
Also see, An LBX Postmortem [keithp.com].
Still requires creation of user "nx"? Noooooo! (Score:2)
I work for a large corporation that uses VNC,and several years ago I tried to install NX at work, hoping to get a speed boost when working remotely. Unfortunately, the creation of a user "nx" was required. I'm not in the IT department, I don't have root access, and they IT department had no interest in deploying NX. So I gave up.
I saw this announcement and hoped that an "nx" user would no longer be required, but it appears this is still necessary. If I could get it installed and it actually worked bette
Re:Still requires creation of user "nx"? Noooooo! (Score:5, Insightful)
You sir, are every IT departments nightmare.
Google going after another MS stronghold - RDP (Score:2)
I work with both MS and Linux servers and, when setting up my own home server, I had a choice between the platforms. Seeing as how I have a TechNet subscription for work/testing purposes Server 2008 is basically free for me so the choice was not one on price but on ease of use and applicability to my needs.
I ended up installing Server 2008 with Linux running under a VM for the occasional usage mostly because of how great Terminal Services is. It gives me a remote desktop through a fast, secure, and very fun
StartUp/Shutdown Time (Score:4, Interesting)
I'm a VNC user, but I realize some of the benefits of NX. (Sound...performance...etc.)
However...I couldn't get past the start-up times. With VNC, I'd 'click' and poof, my applications would be right were I left them, continuing on as if I'd never left. If I closed the window, the applications didn't even know I was gone.
With NX, I'd connect, I'd go through a big start-up process, I'd log in, and wait for my windows to open.... If I wanted to leave, I'd click on the 'I'm leaving now' and it would put everything into a state to where I could come back to it, etc etc. (granted my remote machine was no speed demon.)
So, finally I went back to VNC. I tend to have the window go up and down quite frequently, and the startup/shutdown times of NX were just a deal breaker.
If I was going to use it as more of a truly 'remote terminal' when I'd have it up for hours at a time, then perhaps the heavily loaded ends wouldn't bother me.
Re: (Score:3, Informative)
> my applications would be right were I left them, continuing on as if I'd never left
That's because you never left. That's just how VNC works by default.
> With NX, I'd connect, I'd go through a big start-up process
That's just how NX works by default. It creates a new session every time, while VNC creates sessions on start up and keeps them open. Did you consider looking this up at all? I believe that NX can be made to act like VNC however.
NX via SSH (Score:3, Informative)
Let us not forget that FreeNX and NX in general appears to use SSH as it's only needed port allowing not only normal SSH terminal activity but also NX connectivity using only 1 port with default SSH encrypted packets so they cannot easily reconstruct the transmitted data in the event of an interception.
Still kind of a mess... (Score:3, Informative)
So first, this still requires nomachines nx core, seems like, so it cannot claim to be completely pure.
Secondly, though they don't use Tcl expect, they are still doing the same exact thing, but in python. The problem here is when writing expect stuff, you are already in a bad spot as unexpected input comes up. For example, in trying neatx, I already noted their expect code wasn't expecting a password prompt common in a kerberos environment. And when things go off-the-rails in an expect context, you return to the client an extremely unhelpful, obscure error.
Thirdly, it is all trying to interoperate with NX's rather unfortunate mode of operation where the service is accessed via ssh to another user, even though the goal is just to 'su' to the user you want to be. Considering nx requires you ta have a normal *nix account anyway, I don't get why they implemented this goofy nx user.
NX has long been a source of some frustration to me. FreeNX has been promising, but subject to all sorts of weirdness (sessions suspended being lost because they go to closed, suspneded sessions that cannot be resumed for unknown reasons, etc). I really really want the technology NX has to offer, but all the implementations I've tried thusfar have design decisions that are unfortunate and implementations with mysterious bugs and a user community that is unfortunately weak.
Almost all of this is the fault of the code at the NeatX/FreeNX layer rather than the core. But given the inherently goofy design they are having to emulate, I can't blame them. I would *LOVE* to see an implementation throw out Nomachine's architecture and do a more sane, per user scheme.
Re: (Score:2)
I don't have a problem with the NX client or the free NX server. I love it, in fact. I just wish I could get a damned NX client for the iphone, perhaps with push. run a single app via NX and connect to it from anywhere, just like screen, but for X11. :-)
Re: (Score:2)
Yes and no.
Since this app is open source, there should be no issue, or else a fork will promptly be created.
Re: (Score:2)
There is no substitute for doing this all in OpenGL.
I see what you did there *nudge *nudge* *wink* *wink*. I'm sure Vista's DirectX accelerated desktop is hurt by your comment.
Re:It's no Quartz (Score:4, Informative)
The use of a layer such as Qwartz for Android and Chrome is somewhat independent from Google's working on an NX server though, isn't it? NX is a protocol and client / server code for implementing remote applications with good performance, even over low bandwidth and / or high latency links. It was developed by NoMachine, although others (such as FreeNX and 2X) have also built NX servers. So it really serves a very different (and somewhat orthogonal, though it *is* X11-based) purpose to Quartz.
When you mentioned Quartz, I assumed you meant the compositing layer but Wikipedia (http://en.wikipedia.org/wiki/Quartz_(graphics_layer)) helpfully mentions that both the 2D rendering engining and the Quartz Extreme compositor are sometimes just lumped together as "Quartz". Confusing! So I'm not really sure which you mean ;-)
I'm not clear from the Wikipedia articles whether GL acceleration is yet used by default for Quartz 2D, the rendering engine. though of course the Quartz Extreme Compositor has been doing that for years.
Anyhow, I was going to note that - if you discount X+compiz or whatever as being too heavyweight to be equivalent - the Wayland display server (http://groups.google.com/group/wayland-display-server) is the nearest Linux-land thing I'm aware to Quartz Extreme and it's a pretty neat project at that. Cunningly, Wayland reuses a *lot* of existing X.org infrastructure, it looks like it should be able to support an accelerated X server efficiently as a client *and* they have ideas for what it could be used for even if the rest of the world don't start porting their toolkits to it. So it's a fairly exciting piece of work for the future of display systems on Unix-likes.
Nearest thing to Quartz 2D would seem to be things like Cairo and QT's Arthur. They've been around for a while; I know Cairo can render using GL and would be amazed if Arthur couldn't.
I've no idea what Android runs for its display stack but I'd think that Chrome OS, running on bigger hardware, will have the option of running desktop-class servers and libraries like this. I can't see a move to Wayland by anybody *just* yet but perhaps it's viable for a future revision.
In the meantime, if Google's NeatX makes more seamless, higher performing remote desktop available to more people - that's awesome. One day I might even run it on my server and access it from a netbook - running Chrome OS, perhaps.
Re: (Score:3, Funny)
Re: (Score:2)
What is this, 1995? Who still runs in 16-bit colour?