1. Doing server work from our phones are not optimal, but it is however useful - you are saying that servers only go down when you are at work, good for you, however in the real world the tend to do backflips when the only handful of people with access are on vacation on the other side of the world - this is where having a phone with SSH access is nice.
You're mostly praising network connections. You can use any editor to edit a remote file (you don't necessarily need a remote shell) and you can even install a safe HTTP administrative tool and manipulate your entire server over the web.
2. UltraEdit has a steep learning curve just like VI has - yeah you *might* be able to do notepad stuff right of the bat, but so fucking what? You can do that in Notepad, show me anyone who can do what I can do in VI who has spend less time figuring it out.
You are forgetting a very useful tool that GUI editors make use of: THE EYES. If you pair it with basic language skills, it allows the application to contain OBVIOUS paths to commands, in the form of TOOLBARS, MENU BARS and other graphical representations of commands. It's easy like: "Oh, I want to change something about how I view this document. OH GOD, I WONDER IF THIS 'VIEW' MENU CAN HELP ME".
This argument is always used by most "I'm macho" nerds who think they're really cool for using macho-like old and unproductive tools. And the argument always fails.
3. Your statement about learning curves makes no sense, spending time learning something doesn't require you to give up your life, in fact, spending a bit time learning how to do things a faster way will often save you time over the course of your life.
Faster? HA HA HA.
Me, using my US$ 2500 modern IDE, built for embedded design:
- Start the project wizard
- Choose the proper settings
- Insert my own code inside the basic template
- Compile and simulate/upload using a single click
- Debugging and even code hot-swap are already configured and solved
You, using macho-like tools:
Do you know who achieved more? I DID. Who coded more core, with better conventions and modularization? I DID. That's because you'll spend your precious time trying to fix the tool while I'll spend it USING the tool.
Result: I can finish several projects in a month and spend a lot of times playing with boobies. It's even better considering that US$ (A LOT) - US$ 2500 = US$ (STILL A LOT). I could easily purchase my IDE every week and still be more profitable than using archaic macho-like tools.
And code more, meaning: be more leet than you'll ever be. I will brag about something I built and worked, while you'll still be bragging about being able to use an archaic tool and all you will have achieved is setting up a useless and archaic development environment.
You = "Hello world".
Me = CHANGING THE WORLD, MAKING A DIFFERENCE.