5th July 12:21
The only difference between a "gas" (which includes air) cooled system
and a "liquid" (which could include liquid freon, ammonia, brine) or
a "solid" (ice) cooled system is that the more dense the media (ASSUMING
all other conditions are equal), the better the transfer of heat will be.
But then you get into how well the media contacts the hot surface, flow
rates, turbulence, etc., not to mention the mess, leakage, cost, weight,
space, and so on. Know anything about racing aircraft? The solution
is always to flog the engine harder. The resulting limitation is how to
get rid of all of that heat. Liquid cooled engines tend to be lighter
for a given output because of better transfer from the engine block to
the coolant, but someplace you are still trying to get rid of those BTUs
to the outside air.
We got some VERY LONG LOOKS OF DISPLEASURE when we started replacing the CRTs with plasma.
Well, there is that little fact, yes.
Haven't been to work since the 7th, but there's nothing in the mail, and
no one has tried to firebomb the house, so I guess I escaped that one. [versioning systems]
I think it's a tolerable solution. I know I should be backing things up,
or at least saving a snapshot, and I'm aware of the consequences. For me,
it's a relatively easy choice. I don't use it all the time, but have
learned I'd better do so when I'm doing important stuff.
"project" directories - as well as a habit of doing 'ls -lt' and seeing
what these old files are on a regular basis.
While *nix has always been caseful, some of the old terminal designs did
not place keys in a convenient manner, and you'll find that there are so
many options/commands needed. There might only be 26 letters and ten
digits, but I've used _many_ applications that wanted over 90 features.
That's lower and upper case, and one more roll - metakey who? (It's also
one reason I never got into Emacs, but that's another story entirely.)
That's better than having some "unexpected" happen, and dealing with
multiple versions of UNIX (never mind different breeds of Linux), it
happens all to frequently. Or getting some bizarre output because
the option you chose is BSD rather than SysV, or because HP decided
you really wanted /this/ to happen when you do *that* by default.
The other case is when you are on someone elses system, and the
aliases you depend on are not there, or are different. A _VERY_
common alias is 'alias rm="rm -i"' which turns on the "are you sure"
question for every d4mn file. Sorry, but some day you'll encounter a
system without that alias, fumble-finger something, and then wonder why
the system is lying on the table with it's legs up and eyes closed.
That's not the way to learn to be careful.
[compton ~]$ alias | wc -l
There's nothing wrong with having aliases - most of mine are shortcuts to
a command sequence I'll use on a regular basis. But the problem is when
you use them to overcome a perceived problem - such as the 'rm -i' in
place of 'rm'. Unless you 'unalias' things, they get in the way on scripts
(which may run without a terminal, never mind a live user ready to press
the 'y' key) and that's not good. I mentioned our evaluators looked at
Ubuntu several times as a possible standard distribution (I've got over
2000 systems running Linux at work - I don't need to be running 20
different distributions which their own quirks and warts). I'm under an
NDA, but know that these "let me help you, I know what you really want
to be doing" features knock the scores down even if they are trivial to
fix, because one has to investigate what other dependencies changing
this or that may have. [Super Bowl]
It was in Western Connecticut. Family there called several times to
discuss the TV ads (FedEx, Bud Light "cheese run" , "foreign accents"
"cavemen", and "ability to fly", and the Bud "rocky" were best)/
My niece in Connecticut was bewildered. Her favorites were supposed to
win, and it didn't happen. I was diplomatic, and refrained from openly
exulting. Just as she did in the 1980s.