No, just tools like:
ftp - doesn't need a browser...in fact it predates the browser and GUI.
wget - doesn't need a browser.
Both the above can be run from the CLI and so a box without a GUI.

They need a GUI way to fix things whenever something doesn't work.

No they don't. They just want a GUI way to fix things as they don't understand/consider other ways of interfacing with a computer. I'm always reminded of Scotty in Star Trek IV when he asks to borrow the computer to give the formula for transparent alumin[i]um when I hear this argument - his usual method of interface is spoken words, and when the computer doesn't respond Dr McCoy gives him the mouse for which his first instinct is that it is a microphone. [He's then offered the keyboard, says "How quaint" and then proceeds to use it faster than most people these days.] Scotty didn't give up in a huff because the computer didn't understand his spoken commands, he adapted to the situation.

If you have an automatic car (GUI) and someone tell you to put it into first (CLI manual car solution which is available in all automatic vehicles I've driven) to start off up a steep hill do you go off in a huff and moan that you've got an automatic (GUI) not a manual (CLI) and not bother trying the solution? Similarly going down a steep hill when being told to put it into a low gear (CLI solution) to provide engine braking when you've got an automatic car (GUI, but still has the ability for user gear selection)?

Read: CLI solutions are not quicker nor simpler, unless you already know how!

Exactly the same argument holds for GUI solutions - GUI solutions are not quicker or simpler, unless you already know how.

I'm much balder due to trying to find a GUI solution to problems I could solve with a CLI solution much quicker and simpler.

Why the difference? Simple: I took to computing then the GUI was not much more than an experiment at Xerox and so learnt the use of a keyboard instead of a mouse; when I have to deal with a GUI interface, I struggle going through menus/options to find what I want much more than finding the correct command in a CLI interface

Neither is whipping up a vim or an emacs session to edit some file in /etc/ anybody's idea of fun

Neither is whipping up a registry editor to edit the binary blob of the registry anybody's idea of fun.

It's interesting to consider that Windows 3 used INI files which were text files that cold be edited using a straight forward text editor. The result was that if the configuration was messed up, you could boot a CLI (oh, no, not that idea), either DOS or any other OS that could read the partition, run any old text editor and have a fairly good go at fixing the configuration.

Then came along Win 95 (and repeated with all windows versions) with its registry (a binary blob of a database that held all configurations) that now needs a special program to be able to edit it - GUI based. Which meant if that configuration in the registry is messed up so that the GUI can't run, you couldn't run the registry editor to fix the configuration. Really clever. Solution: take a copy of the registry, but on restoration, it'll destroy all the configuration changes for all programs made since the copy was made; solution: backup regularly and hope main configuration doesn't get messed up...

But it's a red herring anyway. If there was a reason to remove it, sure. But there's no reason to. On the other hand, there was a very good reason for Sony to remove Other OS. Specifically, it was being used to hack the PS3.

[emphasis added]

The tow bars I've seen end in quite a small area which means it will provide quite large pressure (and hence destructive force) when the vehicle is used to reverse into, say, a plate glass window - based on your argument I would now expect every tow bar to be removed on the next service of all cars as they could be used for hacking [in the sense of a machete] into shops and banks, and so have an excellent reason to remove them.

Perhaps like me she would have been one of the first (most likely the first) assistants you remembered as I started watching Dr Who in the early '70s.

Even after watching later, and pre (on video), incarnations of Dr Who, Jon Pertwee + Elizabeth Sladen will always be the doctor and his assistant to me.

Simples:

When the going rate is something like three deciduous forests to buy "one ship's peanut, to obviate the problem and effectively revalue to the leaf...embark on an extensive defoliation campaign and...burn down all the forests" [DA, HHGTTG, 1978] or use something like Agent Orange...

Having PR is not guaranteed to be much better - see, for example, the Alabama paradox - than FPTP. There are further problems with some PR methods (for example STV) whereby if a candidate had won a seat, if their popularity had been larger they would not have won the seat! (A couple of chapters in "Archimedes' Revenge" by Paul Hoffman explain the paradoxes).

At a guess: a progress bar on a transparent background?

Yes. And no.

Copyright protects one implementation - if you can create the same output for the same input without copying the actual implementation, then you're perfectly entitled to do it.

Patent protects all implementations [as far as I can see - regardless of whether the patentee actually though of the implementation or not].

Actually it's about every 7/5 months - DST starts about 1 week after the vernal equinox, but ends about 5 weeks after the autumnal equinox, meaning DST lasts about 7 months, non-DST (sun-time) lasts about 5 months.

It is get up an hour earlier in Winter, so that when you've been getting up at 5am in DST, when DST ends, you then get up at 4am instead, which is what 5am in DST equates to in non-DST - ie you have not changed your sleep schedule with respect to the sun (and the slowly changing daylight), only the clock (which has changed with respect to the sun).

Thus when DST ends, you will then have an hour less in the evening as you'll also go to bed an hour earlier (with respect to the clock, not the sun) when it's dark anyway, along with going to work an hour later (giving you an extra hour in the morning).

If you want light at the end of the day, try moving further North...you'll get light long into the night - far enough north and you'll get 24 hours of the stuff (in the summer when the DST is in effect).

Problem solved: instead of changing clocks, make school/work/pub closing times all run one hour earlier.

Same effect, just it also makes the sun correct so that the middle of the day (and daylight hours) is (approx) 12 noon not 1pm every day (or 2pm on double summer time).

Going to sub-Sahara Africa is an interesting experience - dawn is (approx) 6am +/- 30 mins, dusk is (approx) 6pm +/- 30 mins all year round - none of this day light saving clock changing.

All right --- Sony appears to be guilty of perjury after filing a takedown notice for someone else's work.

[Emphasis added] Does that mean the actual creator of the work can go after Sony for piracy (sic) and do them for copyright infringement - if Sony are indeed claiming to own the copyright on the work they created and thus for which they have copyright?

...One thing you do do is prevent good software from being written...

That explains the quality of MS Software then...

...And all OSS software which is free (as in gratis)?

...in their fancy new interface they make you Copy by clicking on Paste!

Why does this surprise you? Windows 95 (98 def had?) introduced the START button you have to click to shutdown the computer - you had to click START to STOP the computer (XP as well?) - so why are you confused over needing to click PASTE to COPY?

Just as Vista removed the start button (presumably to avoid the stupidity of having the click the opposite to what you want to do) expect a new version of the ribbon to remove the Paste sub-menu and replace it with an icon of some sort

What the research actually concluded was that the total cost of ownership can vary...training and support.

My one objection to most similar studies...is that switching from, say, MS Office 2003 to 2007...is considered to take little or no training...but switching to OpenOffice is projected to incur significant retraining expenses...

A few years ago a large UK retailer upgraded their staff laptops to Windows XP. All the [laptop] staff went on "XP training". Changing to "what you know" doesn't necessarily mean no training costs; proves your point, and that was in use of WIndows itself - which I seem to always hear as touted as not needing any training when "upgrading".