Have a vetrinary surgeon remove a steak without killing the animal. See if the steak is any good. Resist the urge to immediately eat the rest of the animal.
There, problem solved, without all the high-tech nonsense.
You can graze animals on ground that is rocky and hilly. You can not operate modern farm equipment there.
The best land usage is that we use the hilly areas for free-range grazing, the nice flat areas for growing plants, and various crummy areas for houses.
Of course, we do: use the nicest farmland for houses, ignore the hilly areas, and use the crummy-yet-flat areas to grow food for feedlot animals. Our usage of the best farmland for houses is probably the biggest environmental error we make; we are bound to this error by economic factors related to the "tragedy of the commons".
First of all, there can be no cure. This is a simple fact that would be obvious if you understood how AIDS worked.
Second of all, we know perfectly well how to avoid getting AIDS. Aside from a few extremely unlucky people, only idiots get infected.
There are so many other diseases we could cure, including ones that wouldn't be a total wasted effort. There are normally-communicable diseases like tuberculosis that are coming back to haunt us in drug-resistant forms. There are mosquito-borne diseases. Heart disease kills many, including people who don't make foolish dietary choices. Mental illnesses, such as schitzophrenia and maniac-depression, are common and destructive. Then there are all the numerous injuries, like severe burns.
In the USA, people expect perfection. They demand it. If they don't get it, and even sometimes when they do, they file a lawsuit. Sometimes this is a multi-million-dollar jackpot. Other times, the insurance company quietly settles for a damn fine chunk of change.
This means the doctors have to pay for insurance. Some need to pay over a million dollars per year. Guess how they get the money.
The fix is easy: eliminate all medical liability. If the doctor is incompetant, he should just lose his license. If the doctor is evil, he should just go to jail. If the patient wants a payout upon injury, let them buy their own insurance to cover such injuries.
Winners: nearly all patients and nearly all doctors Losers: trial lawyers, incompetant doctors, and evil patients Mixed: insurance companies
For non-emergency, all costs must be disclosed as early as possible. Individuals pay out of their pocket. There is no mandate to treat people who can't pay. Insurance is prohibited, because it acts to reduce price competition.
For true emergency, the government pays until the emergency has passed. All people get treated as needed. (excepting unusual mass-casualty situations, where the hospital should pick people likely to survive and people who are needed to support families)
Simple broken arms are not true emergencies. Normal childbirth is not an emergency. To be an emergency, the person must be in immediate danger of preventable harm. In other words, your end result will be worse if you don't get immediate treatment. Anything that can wait a few hours is not an emergency.
Odd that nobody ever shows a decent theme, no? Excuse me for concluding that no decent themes are available or even possible.
While getting stuff done I do happen to stare at my computer. That's rather normal for sighted people.
Getting stuff done quickly means having appropriate contrast. The contrast should make things stand out as needed, without being needlessly distracting.
Getting stuff done quickly means having shapes that can be quickly recognized by the brain at a very low level. A rectangular outline (button, menu, window, tab, etc.) among many other rectangular outlines is hard to pick out, particularly if colored the same. A slightly more organic look, with rounded corners, is easier to pick out from the noisy background.
Note: MacOS X appears to be decent in this regard, but nothing special. The upper menu thing however is a terrible mix of app-supplied and system-supplied things. The OS also makes it terribly easy to leave an app running without realizing that the app is running. The new thing at the bottom of the screen seems really out of place and it awkwardly fails to span the full width of the screen. Use of the background wallpaper as a "desktop" is entrenched idiocy; a busy user will quickly lose sight of the desktop under a pile of apps.
That's not the worst of it. It wouldn't even be all that bad if they'd shove the toolbar buttons together.
Check out the scrollbars! The drop-down-combo-box is like that Motif crud that should never have seen the light of day. There are huge contrast problems, with fairly dark grey (depressing) all over except for white text boxes that just scream at you. The fonts don't fit very well. There are alignment problems.
If the looks are that bad, what about the usability? In a GUI, there is far more than meets the eye. Timing matters. A good GUI is forgiving of people who are slightly off track when quickly navigating through menus.
I wonder if it can be fully configured via the GUI without restarting. (no.Xdefaults, no hand editing, no "GUI" interface to an XML tree that is practically the same as hand editing but without the ability to add comments, etc.)
Content production: you need Windows-based professional video authoring tools to support the format. (Is this in their interest? Really? Would acceptance of the format change competition?)
Server: you need an IIS plug-in to serve the video.
Client: you need Microsoft to provide a mapping from MIME type to codec download URL or, better yet, provide the codec with the OS.
1. Digital Fax system 2. SharePoint services 3. Remote desktop / assitance 4. Group Policies 5. Exchange
For less than 40 users??? Dude, you need a fileserver appliance and either an email appliance or outsourced email.
Probably the appliances run Linux internally, but you don't need to know. You admin them via a web interface. They don't fail for mysterious reasons involving fuckups or malware.
In a place with only 40 users, desktop assistance is a wonderful opportunity to get off your ass and do 100 feet (30 meters) of this excercise we call "walking". It's good for your health, probably way faster to set up, and provides the human touch that you need to be providing for career reasons.
I'm tempted to say that GNU makes **everything** ugly, but actually GNOME isn't bad if you play with the settings for a bit. (hint: you can ditch the second toolbar and thicken up the other one)
There are the known things, and the things for which we'd have to trust Hans. (Hans appears to be telling the truth about at much of this at least)
Suspected: had an affair Suspected: transferred lots of money to that guy Suspected: various criminal attempts to rid herself of Hans Known: left Hans Known: took children away from Hans Suspected: tried to ensure Hans wouldn't see his children Known: made divorce into a cruel battle to take everything
It's not as if this were a girlfriend. They were married. Wedding vows should last until death do you part.
(if they were unmarried, I'd say Hans deserves to fry)
The Linux driver has to deal with about 10 different types. There is no standard endianness. Even the superblock and inode structures differ. Here is the list of varients that Linux supports:
old
Old format of ufs default value. Supported as read-only.
44bsd
Used in FreeBSD, NetBSD, OpenBSD. Supported as read-write.
ufs2
Used in FreeBSD 5.x. Supported as read-only.
5xbsd
Synonym for ufs2.
sun
Used in SunOS (Solaris). Supported as read-write.
sunx86
Used in SunOS for Intel (Solarisx86). Supported as read-write.
hp
Used in HP-UX. Supported as read-only.
nextstep
Used in NextStep. Supported as read-only.
nextstep-cd
Used for NextStep CDROMs (block_size == 2048). Supported as read-only.
On a typical Windows PC, there will be many different pieces of malware fighting over this. The malware also fights over your home page and numerous other things.
If the processor supports the feature, it should be available to the OS. If the OS also supports the feature, it should be available to the apps. For apps that are unaware of the feature, the OS should let the user decide.
Does the BIOS actually make the CPUID instruction lie about the feature? (allowing the BIOS to hide the feature from the OS) If so, is it merely hidden or actually disabled? In other words, could the OS just use the feature despite whatever the CPUID reports? Does the BIOS instead make the feature non-functional?
Unless your chip is very recent, the timestamp counter speeds will vary.
Unless your Linux kernel is very recent, this condition will not be detected automatically. Linux will assume that the discrepency means you are losing clock ticks.
You can try kernel parameters like clocksource=pmtmr to fix it. Good luck, you may need it...
The BIOS vendors disable this power-saving feature because there are Windows games that, like Linux, assume the timestamp counters don't vary in speed.
Also common is 16:10. Some displays can rotate, so we need also need that: 3:4, 9:16, 10:16.
Arbitrary support would be good.
Let me say how to deal with mismatch: letterbox, letterbox-like but shifted up or left, letterbox-like but shifted down or right, stretched (with or w/o maintaining aspect ratio for images), cropped...
Also, don't crash when I try to force this via badly editing the XML.:-)
There are many unknowns. Start with the 3 dimensions of space. To precicely locate something in space, you have a trade-off with time. You also have a limit on the size of the antenna array that can be carried, and size is also critical for spacial accuracy.
I don't think you'll be getting accurate targeting info out of that. Remember, the suggestion was that passive measures could be used to target a stealth aircraft.
Slashdot Mirror
"animal husbandry"?
I really don't want to know...
Have a vetrinary surgeon remove a steak without killing the animal. See if the steak is any good. Resist the urge to immediately eat the rest of the animal.
There, problem solved, without all the high-tech nonsense.
You can graze animals on ground that is rocky and hilly. You can not operate modern farm equipment there.
The best land usage is that we use the hilly areas for free-range grazing, the nice flat areas for growing plants, and various crummy areas for houses.
Of course, we do: use the nicest farmland for houses, ignore the hilly areas, and use the crummy-yet-flat areas to grow food for feedlot animals. Our usage of the best farmland for houses is probably the biggest environmental error we make; we are bound to this error by economic factors related to the "tragedy of the commons".
Not that they deserve it, but this is necessary to help them resist bribes.
First of all, there can be no cure. This is a simple fact that would be obvious if you understood how AIDS worked.
Second of all, we know perfectly well how to avoid getting AIDS. Aside from a few extremely unlucky people, only idiots get infected.
There are so many other diseases we could cure, including ones that wouldn't be a total wasted effort. There are normally-communicable diseases like tuberculosis that are coming back to haunt us in drug-resistant forms. There are mosquito-borne diseases. Heart disease kills many, including people who don't make foolish dietary choices. Mental illnesses, such as schitzophrenia and maniac-depression, are common and destructive. Then there are all the numerous injuries, like severe burns.
In the USA, people expect perfection. They demand it. If they don't get it, and even sometimes when they do, they file a lawsuit. Sometimes this is a multi-million-dollar jackpot. Other times, the insurance company quietly settles for a damn fine chunk of change.
This means the doctors have to pay for insurance. Some need to pay over a million dollars per year. Guess how they get the money.
The fix is easy: eliminate all medical liability. If the doctor is incompetant, he should just lose his license. If the doctor is evil, he should just go to jail. If the patient wants a payout upon injury, let them buy their own insurance to cover such injuries.
Winners: nearly all patients and nearly all doctors
Losers: trial lawyers, incompetant doctors, and evil patients
Mixed: insurance companies
With that, people don't bother to shop around.
The law ought to be as follows:
For non-emergency, all costs must be disclosed as early as possible. Individuals pay out of their pocket. There is no mandate to treat people who can't pay. Insurance is prohibited, because it acts to reduce price competition.
For true emergency, the government pays until the emergency has passed. All people get treated as needed. (excepting unusual mass-casualty situations, where the hospital should pick people likely to survive and people who are needed to support families)
Simple broken arms are not true emergencies. Normal childbirth is not an emergency. To be an emergency, the person must be in immediate danger of preventable harm. In other words, your end result will be worse if you don't get immediate treatment. Anything that can wait a few hours is not an emergency.
Odd that nobody ever shows a decent theme, no? Excuse me for concluding that no decent themes are available or even possible.
While getting stuff done I do happen to stare at my computer. That's rather normal for sighted people.
Getting stuff done quickly means having appropriate contrast. The contrast should make things stand out as needed, without being needlessly distracting.
Getting stuff done quickly means having shapes that can be quickly recognized by the brain at a very low level. A rectangular outline (button, menu, window, tab, etc.) among many other rectangular outlines is hard to pick out, particularly if colored the same. A slightly more organic look, with rounded corners, is easier to pick out from the noisy background.
Note: MacOS X appears to be decent in this regard, but nothing special. The upper menu thing however is a terrible mix of app-supplied and system-supplied things. The OS also makes it terribly easy to leave an app running without realizing that the app is running. The new thing at the bottom of the screen seems really out of place and it awkwardly fails to span the full width of the screen. Use of the background wallpaper as a "desktop" is entrenched idiocy; a busy user will quickly lose sight of the desktop under a pile of apps.
That's not the worst of it. It wouldn't even be all that bad if they'd shove the toolbar buttons together.
.Xdefaults, no hand editing, no "GUI" interface to an XML tree that is practically the same as hand editing but without the ability to add comments, etc.)
Check out the scrollbars! The drop-down-combo-box is like that Motif crud that should never have seen the light of day. There are huge contrast problems, with fairly dark grey (depressing) all over except for white text boxes that just scream at you. The fonts don't fit very well. There are alignment problems.
If the looks are that bad, what about the usability? In a GUI, there is far more than meets the eye. Timing matters. A good GUI is forgiving of people who are slightly off track when quickly navigating through menus.
I wonder if it can be fully configured via the GUI without restarting. (no
You need to pick the 3 parts separately to get something nice.
Start with Clearlooks, then choose to customize it. Make the
following choices:
controls: Clearlooks
window border: Lush
icons: GNOME
Probably Red Hat has a different name for "Clearlooks".
I think they trademarked the name they use.
Are all the pieces there?
Content production: you need Windows-based professional video authoring tools to support the format. (Is this in their interest? Really? Would acceptance of the format change competition?)
Server: you need an IIS plug-in to serve the video.
Client: you need Microsoft to provide a mapping from MIME type to codec download URL or, better yet, provide the codec with the OS.
The big-iron stuff, from mainframes right down to UNIX workstations, suffered severely for making this mistake.
He who owns the desktop controls the protocols, and thus the servers.
Let's look at that list:
1. Digital Fax system
2. SharePoint services
3. Remote desktop / assitance
4. Group Policies
5. Exchange
For less than 40 users??? Dude, you need a fileserver appliance
and either an email appliance or outsourced email.
Probably the appliances run Linux internally, but you don't
need to know. You admin them via a web interface. They don't
fail for mysterious reasons involving fuckups or malware.
In a place with only 40 users, desktop assistance is a wonderful
opportunity to get off your ass and do 100 feet (30 meters) of
this excercise we call "walking". It's good for your health,
probably way faster to set up, and provides the human touch that
you need to be providing for career reasons.
Look at this painfully ugly mess:
g
http://www.gnustep.org/images/full-screenshot1.pn
http://en.wikipedia.org/wiki/Image:Gnustep.png
I'm tempted to say that GNU makes **everything** ugly,
but actually GNOME isn't bad if you play with the
settings for a bit. (hint: you can ditch the second
toolbar and thicken up the other one)
They know that open source projects CAN'T pay the royalties. This keeps us out.
There are the known things, and the things for which we'd have to trust Hans.
(Hans appears to be telling the truth about at much of this at least)
Suspected: had an affair
Suspected: transferred lots of money to that guy
Suspected: various criminal attempts to rid herself of Hans
Known: left Hans
Known: took children away from Hans
Suspected: tried to ensure Hans wouldn't see his children
Known: made divorce into a cruel battle to take everything
It's not as if this were a girlfriend. They were married.
Wedding vows should last until death do you part.
(if they were unmarried, I'd say Hans deserves to fry)
If I were on the jury, I'd vote innocent even if I did think he killed her. (and I do think that)
She was NOT a good woman, by a long shot.
old
Old format of ufs default value. Supported as read-only.
44bsd
Used in FreeBSD, NetBSD, OpenBSD. Supported as read-write.
ufs2
Used in FreeBSD 5.x. Supported as read-only.
5xbsd
Synonym for ufs2.
sun
Used in SunOS (Solaris). Supported as read-write.
sunx86
Used in SunOS for Intel (Solarisx86). Supported as read-write.
hp
Used in HP-UX. Supported as read-only.
nextstep
Used in NextStep. Supported as read-only.
nextstep-cd
Used for NextStep CDROMs (block_size == 2048). Supported as read-only.
openstep
Used in OpenStep Supported as read-only.
Malware replaces the default search all the time.
On a typical Windows PC, there will be many different pieces of malware fighting over this. The malware also fights over your home page and numerous other things.
I mean really WTF?
If the processor supports the feature, it should be available to the OS.
If the OS also supports the feature, it should be available to the apps.
For apps that are unaware of the feature, the OS should let the user decide.
Does the BIOS actually make the CPUID instruction lie about the feature?
(allowing the BIOS to hide the feature from the OS) If so, is it merely
hidden or actually disabled? In other words, could the OS just use the
feature despite whatever the CPUID reports? Does the BIOS instead make
the feature non-functional?
Lots of OS-level things are controlled by flags in the headers of executables.
Unless your chip is very recent, the timestamp counter speeds will vary.
Unless your Linux kernel is very recent, this condition will not be detected automatically. Linux will assume that the discrepency means you are losing clock ticks.
You can try kernel parameters like clocksource=pmtmr to fix it. Good luck, you may need it...
The BIOS vendors disable this power-saving feature because there are Windows games that, like Linux, assume the timestamp counters don't vary in speed.
Powerpoint can do 16:9 now.
:-)
Also common is 16:10. Some displays can rotate, so we need also need that: 3:4, 9:16, 10:16.
Arbitrary support would be good.
Let me say how to deal with mismatch: letterbox, letterbox-like but shifted up or left, letterbox-like but shifted down or right, stretched (with or w/o maintaining aspect ratio for images), cropped...
Also, don't crash when I try to force this via badly editing the XML.
There are many unknowns. Start with the 3 dimensions of space. To precicely locate something in space, you have a trade-off with time. You also have a limit on the size of the antenna array that can be carried, and size is also critical for spacial accuracy.
I don't think you'll be getting accurate targeting info out of that. Remember, the suggestion was that passive measures could be used to target a stealth aircraft.
Ask for a bare-metal discount. It's like buying a PC without Windows and writing your own OS.
Surely the UK can write radar software? You could then refuse to give it to the USA.
The aircraft is still a nice piece of hardware.