I use it daily and it's a timesaver. The syntax for creating a pull request from a branch on a non-forked remote forces you to always pass the -h option, but beyond that it's amazingly simple.
This really depends on your situation. If you are writing a reusable app, then you probably want both unit tests and a sample project to run integration tests against.
I worked pretty closely with a designer just recently. We went from throwing designs over the wall, to basic git based version control. We found that it was a pretty enjoyable workflow for the both of us. It allowed the designer to have more control over the end product, since he didn't need to ask me to update images.
We got to the point where he'd own all of the HTML and CSS, as long as I had certain ids and classes to hook my Javascript into. After we got CI and CD going, he's start pushing out new designs several times a day, giving us a pretty quick turn around time.
I never asked him to use the command line, since Tower handled most of the stuff he'd do. I wouldn't ask him to learn all of git, just as how I'd be frustrated if I had to learn all of Photoshop. I wouldn't be opposed to doing some basic work, like changing the color on the background layer.
This isn't very helpful in your specific problem, but typically servers don't have graphical capabilities. So much so, that I was a little baffled when I read that you VNC'ed into one. Instead your local toolchain interacts with the remote.
If I wanted to paste something in a file remotely, I'd open it in my local editor (which can ssh into remote machines). If I needed to transfer files back and forth, I'd use an FTP client (Filezilla works cross-platform).
Are you saying you've found a way to remotely browse the filesystem of your Ubuntu box from within windows (without resorting to FTP?). As in, something that ties into windows explorer and lets you deal with remote files as though they were local?
If so, please point me to it.
But that's sort of the point I'm trying to make. If the Ubuntu team wants to get Windows devs to try out their thing, they need to make stuff like this completely painless. To the point of building a "Windows Kit" that you simply install at your end and it hooks you up with a complete set of tools you need to interact with your remote server.
Yes, it's called WinSCP: http://winscp.net/eng/index.php. It makes the remote filesystem appear as if it's just a local filesystem (if you choose the explorer interface type).
Look into filesystems over SSH. There are things like that for windows and they work okay (though what's wrong with using an FTP/SFTP client?)
I think you're missing the point that admining a Linux server is different. The complete set of tools you need to interact with a remote Linux server is: an SSH client.
I've used ubuntu on servers before and it is quite painless. You've inflicted a fair ammount of pain on yourself by running a graphical interface on a server.
As others have stated, spending 15 minutes learning about the linux commandline will save you a ton of time, effort, and pain.
The GUI was an attempt to alleviate the pain caused by years of having to poke at Linux boxes through a terminal. As far as I'm concerned, it's still orders of magnitude better than having to type out keyboard commands to navigate around the filesystem.
It's just a shame that the tools to do it remotely aren't up to scratch.
I'm curious how you respond to the idea that Jesus didn't exist as a historical figure. The argument for this idea typically points to the lack of a first hand account of Jesus, with the first accounts appearing decades after his alleged death. That would make it a little difficult for the Roman authorities to provide evidence that Jesus was not supernatural.
The idea that Jesus didn't exist as a historical figure is laughable and people who defend that idea normally end up tying themselves in knots. We have four independent eyewitness accounts, sometimes using the same sources, sometimes not, mentions by a Jewish historian, Roman historians and prominent sceptics - who by the way mock the nature of the resurrection, not the existence of the person. I guess it's kind of stupid to deny the existence of someone so close to the time they were around.
One of the "biased" sources - Luke - is widely regarded by people who know what they're talking about (like Sir William Ramsay who spent a lifetime digging up the Middle East) as the finest, most accurate historian who ever lived.
The fact that the first written accounts of Jesus appeared only decades after his execution is extraordinary to scholars of ancient literature who are used to dealing with gaps of many _centuries_, sometimes even a millenium. I can't remember offhand what the earliest copy we have of Tacitus is for example but I think it's a good 800 years after he wrote it.
When I apply the same methods of the Jesus mythers to Alexander the Great, Julius Caesar, Tacitus, Mohammed and even Abraham Lincoln, guess what? None of them ever existed either.
You need a great deal of hand-waving, special pleading and outright dishonesty to be a myther. Robin Lane Fox, who is certainly no Christian, is at least honest when he reads the account of John and concludes that it's an eyewitness account. Would that Dawkins and Price had the same integrity.
I know that the meaning of REST has been diluted a lot, but this mostly RPC with pretty URLs.
I don't understand why they don't support PUT and DELETE. They are already using jQuery on the HTML implementation of their API site, so could use its Ajax library to provide cross-browser PUT and DELETE. If they wanted browser usable methods, they could have used the standard "_method" parameter along with POST, and convert it server-side.
This actually makes it a lot less discoverable for those of us not using the HTML view. For instance, when using curl to browse to /vi/client/list, I expect to get a list of clients. Instead, I get the following (I'd prefer to show JSON here, but I get a 500 when I try it.):
There's also the issues of assuming a certain view in the end representation, including CSS and JS in their HTML representation, and having different default formats for different resources. All these make working with the API annoying.
https://github.com/defunkt/hub