I like the directory-based setup. It's very easy to specialize by machine, OS type, and so forth. I'm always tempted to write something to let me manage the entries in it better, but so far managing them manually hasn't pissed me off sufficiently to actually go do that.
I'm usually an emacs guy for editing source and a vi guy for editing system files. If I need to make a quick change to source, I'll fire vi up for that, too. This always seems odd to me, but I try not to let it bother me.
I never liked that newfangled vim. It's far too... colorful. I usually swap it out for nvi, which is much more vi-like. Distributions (like Redhat) that install pico as the default editor make me punch someone. Maybe the guy who thought pico should be considered in any way an acceptable UNIX editor. I always have to swear, abort back to the command line, and export VISUAL=vi.
Oh, I see. It started under EDS auspices a few years back. Pretty light on details other than that, but let me guess, EDS proposed Citrix as a solution right out of the gate and set up the server on some 286 that they found in Ross Perot's attic. Am I getting warm? I'm pretty sure I'm getting warm, because EDS is a one-trick pony, and their trick sucks. Doesn't matter if you're setting up an accounting system or a next generation war ship, EDS will find SOME way to install Citrix on it. I'd say "and make it suck" but that's kind of redundant when you're talking about Citrix!
Too bad for the Government EDS is pretty much the only game in town if you need some IT contracting done. Enjoy your Citrix!
Sure an electric would be fine for the daily commute and even most of my drives in the mountains don't usually go over a couple hundred miles tops, but there are some use cases in the middle of the country where even if you had ample recharging stations you'd probably still want a conventional car.
Back in the day I had an RX7 that was prone to flooding. I got pretty good at pulling the fuel injector fuse, starting it and plugging it back in before the car stalled. If you had an extra few hundred bucks laying around you could also install a switch that would cut the power to the injectors from the dash. That might not be a bad idea on some of these newfangled cars -- a toggle switch with a direct method of killing the engine with no computers in the way. The RX7 also had a throttle that was prone to sticking, but it was pretty easy to pop it into neutral, pull to the side, turn off the engine, pop the hood and hose down the throttle assembly with silicone lubricant whenever that happened (That was a VERY fun car to drive!)
Yet you really don't see similar kool-aid drinking driving the replacement of COBOL. You'd think by sheer chance some dimwit PHB would come in and arbitrarily decide "Oh let's replace all that COBOL code with something written in Ruby on Rails by an intern," because he'd just read about Ruby on Rails on PC magazine and was impressed with how quickly you could develop a web-based "Hello World" application.
Admittedly a probably largish number of PHBs have attempted that and subsequently been fired by incompetence, but you'd think enough of those projects would limp along because they've already spent so much money, effort and time that to admit defeat would mean admitting gross incompetence at every level of management straight up to the CIO. Which, I'm pretty sure, is why Lotus Notes and Citrix are still around.
Funny story, back in the 90's when IBM was replacing Profs with Lotus Notes, some dim-witted PHB decided "Oh well PCs can do anything that mainframes can do, so let's write a Lotus Notes replacement to RETAIN!" RETAIN being the mainframe-based app they use for trouble ticket tracking and bug fixing across, I'm pretty sure, all their products. Well long story short, that project went on for a couple of years and then quietly disappeared. A decade later, they were still using and actively maintaining RETAIN. I wouldn't be surprised if it were still being used and maintained to this very day, even after IBM's acquisition of Rational.
Hmm. I wonder if I wrote an app that was nothing BUT progress bar, if people would go for it.
Some developers have already come to the conclusion that installation is a prime advertising timeslot. So even if anyone was inclined to write a progress bar, it'll still end up ad-laden and annoying.
The faster I go, the behinder I get. -- Lewis Carroll