Okay, I shouldn't do this, I know; but its monday.
> What pisses me off about RedHat is how deliberate their embrace-and-extend design policies are.
No. Sorry, no. Not even a bit. Generally, the design approach is something along the lines of "What the $#**! Why is it doing that? That's absurd. It breaks (i18n/printing/USB/my toaster). Well, fix it. Yeah, but the only way to fix it breaks (backwards compat/non-ANSI C/5 year old packages). Damned if you do, damned if you dont. Grrr, go with the future compatible stuff."
> If there is one thing the web needs right now, it is freedom from the vision of the semantic web, and all those other idiotic visions keeping us from progressing further.
right...
nope, you're wrong. There is simply no way for the web to be what it needs to be if it doesnt become semantic.
I dont think you understand my real objection. I was tired when I wrote the first post. Production language are "write-only". You can't manipulate them programatically. This is bad.
CURL is a production based presentation languge, ala PostScript. There is NO way to do anything meaningful to it once it is written, without using a human mind, and maybe not then.
Production languages take that whole little layout/content seperation theory you may have heard of, and ignore it completely. Crap, crap, I say!
What annoys me, and always has, is that people associate namespaces with OO. It makes no sense. Namespaces are a scope construct, and would be increadibly useful in procedural languages, if people would just add them.
What annoys me more, is 'OO' languages which tie namespaces to modules or objects, instead of the other way 'round.
The flipping of the earth's magnetic field is pretty well understood:
Ice Ages, and thaws, affect the distribution of mass upon the surface of the plannet just enough to affect the spin rate. Changes in the spin rate disrupt the coriolis induced iron magma currents in the core, which are the primary cause of earth's large magnetic field, and the field collapses into chaos.
When these currents stabilize, having adjusted to the new spin rate, the field becomes coherent again. The polarity of the field when it reaserts is a toss up.
So, when people talk about the earth 'flipping' its polarity, they often overlook that about 1/2 the time, the polarity after a reasert is the same as it was before the field collapsed.
>> How could you be sure they had not put a back door in ?
Read the code? (Some people are idiots, I swear.)
-- Crutcher -- #include <disclaimer.h>
My Guess, Sealed Personal Dirigibles.
on
What is 'IT'?
·
· Score: 2
Really, no joke.
A mechanicaly operated (pedaled) sealed system personal dirigible, with a mechanical gas pump.
Cost efficient, fun, difficult to regulate, cheap to mass produce once the design is right, and requiring serious changes to archetecture to take advantage of them.
The whole promise of retinal scanning displays is that they are 1) incredibly sharp, and can (theoretically) 2) be squeezed into much small packages than LCD based systems (because LCD systems have to have an array/somewhere/ and RSD's don't.
True, this is currently only about the size of a normal LCD headset, but it will shrink, and I want one!!! (the little detail about see-through visual overlays has some/very/ interesting UI posibilities. Imagine themeable worlds in 20 years!)
Think of the sheer volume of time that must be spent creating the material for a course, then the additional volume of time that must be spent editing and verifying this material, and then the additional chunk that must be spent making sure that this is all taught in a consistent and flowing manner.
Now, consider that individuals who have the skills to accomplish the first, second, and third tasks/well/ are usually found in seperate groups (programmers, editors, teachers); that each group's time is very valuable (in terms of average pay); and that individuals who fall far into multiple of these groups have an even/higher/ value placed upon their time.
People do the hard tech stuff, because it is fun. People write docs because they have to. People edit docs because they are paid to. Noone reorders docs for 'fun', 'cause it sucks, and they could be playing with code.
Well, not really, but this is the basic solopsistic problem.
Since your only interaction with the world is through your senses, how can you verify that it is as it seems, or even exists at all;/without/ using your senses?
The best answer that anyone ever came up with is "I refute it thus" and kicking a rock. (not making this up). In reality, there is no true answer, indiviudals must make the "leap of faith", or the "leap of presumption" at least, and presume that the world is more or less as it appears to be.
Since true signatures validity can only be 'proven' by either A) testimony to the fact (which doesn't really require the signature, after the testimony) or B) the voice of 'experts'; the 'experts' can be cryptography experts, and can, like the hyndwriting experts, testify about the/probability/ of error.
And it is ultimately only about how probable it is, since you can't prove anything.
The KDE League/GNOME Foundation crossover, where a portal is opened between two parallel developer communities so that they may avvert the Mighty Siesmic Network!
Preorders availbale now, comic on shelves June 2001.
Note:
There is a large difference between voluntary categorization, which is the dewey deciaml system (voluntary by the library); the sections in bookstores (voluntary by the vendor) and MANDATORY labeling.
If you want to use pithy metaphores, its like saying, "You, you like brocoli, so you have to change your name to 'brocoli-lover' so that we can tell who you are", or "You're a jew, you have to wear this little star."
Vaporware? Can you pass the crack pipe? They've been working on this, and we've be reading about it, for some time.
This stuff is so cool, btw. Why use slow balistic calculations in games, when you've got enough space to store a lookup table! (Okay, that's rediculous, but this is still coolness)
1) Process clustering - This beowulf, it is designed to rip every last shred of CPU time out of boxen. It is a VERY custom, machine dependant thing. A good B-cluster will be so hand tweaked as to be almost unrecognizable as what ever distro.
2) Server clustering - this is failover stuff, and distros can do this much better. Most people call it something like High Availability. But you are still likely to teak it up.
This is not a very good question, because clusters tend to be so custom. Its like asking: "Whats the best frame to base a kit car on?" There/is/ a valid answer, but it simplifies more than it educates.
Well, no, not really.
Microsoft can't point to/current/ competetors, but only to competetors during the period in question (when Linux most deffinately was NOT one)
It does require registration, though there is an 'anonymous' registration option, that sends only your hardware archetecture (so that the right rpms get sent) and an email address. It is one of the free levels of service. (of which there are several)
There is no distinction between 'official' and 'unofficial' ISO images. Its all the same ISO. And the daemon doesn't do anything unless you tell it to (but it is running).
The easyest fix is to just run up2date, and update the 'up2date' package, which owns the daemon.
It damn well does what you tell it to. Linux is NOT CLI, linux is a kernel, and a pretty cool one at that.
And computers need kernels. Now, you can put any layer on top you want, and, BTW, GUI's ALWAYS need an extra layer (its just hidden from you sometimes).
Slashdot Mirror
Okay, I shouldn't do this, I know; but its monday.
> What pisses me off about RedHat is how deliberate their embrace-and-extend design policies are.
No. Sorry, no. Not even a bit. Generally, the design approach is something along the lines of "What the $#**! Why is it doing that? That's absurd. It breaks (i18n/printing/USB/my toaster). Well, fix it. Yeah, but the only way to fix it breaks (backwards compat/non-ANSI C/5 year old packages). Damned if you do, damned if you dont. Grrr, go with the future compatible stuff."
> If there is one thing the web needs right now, it is freedom from the vision of the semantic web, and all those other idiotic visions keeping us from progressing further.
right...
nope, you're wrong. There is simply no way for the web to be what it needs to be if it doesnt become semantic.
I dont think you understand my real objection. I was tired when I wrote the first post. Production language are "write-only". You can't manipulate them programatically. This is bad.
CURL is a production based presentation languge, ala PostScript. There is NO way to do anything meaningful to it once it is written, without using a human mind, and maybe not then.
Production languages take that whole little layout/content seperation theory you may have heard of, and ignore it completely. Crap, crap, I say!
What annoys me, and always has, is that people associate namespaces with OO. It makes no sense. Namespaces are a scope construct, and would be increadibly useful in procedural languages, if people would just add them.
What annoys me more, is 'OO' languages which tie namespaces to modules or objects, instead of the other way 'round.
-- Crutcher --
#include <disclaimer.h>
The flipping of the earth's magnetic field is pretty well understood:
Ice Ages, and thaws, affect the distribution of mass upon the surface of the plannet just enough to affect the spin rate. Changes in the spin rate disrupt the coriolis induced iron magma currents in the core, which are the primary cause of earth's large magnetic field, and the field collapses into chaos.
When these currents stabilize, having adjusted to the new spin rate, the field becomes coherent again. The polarity of the field when it reaserts is a toss up.
So, when people talk about the earth 'flipping' its polarity, they often overlook that about 1/2 the time, the polarity after a reasert is the same as it was before the field collapsed.
-- Crutcher --
#include <disclaimer.h>
>> How could you be sure they had not put a back door in ?
Read the code? (Some people are idiots, I swear.)
-- Crutcher --
#include <disclaimer.h>
Really, no joke.
A mechanicaly operated (pedaled) sealed system personal dirigible, with a mechanical gas pump.
Cost efficient, fun, difficult to regulate, cheap to mass produce once the design is right, and requiring serious changes to archetecture to take advantage of them.
I'd buy one, wouldn't you?
-- Crutcher --
#include <disclaimer.h>
Never mind, they edited the article to fix this.
It was funny, though.
-- Crutcher --
#include <disclaimer.h>
I dont think anything else needs to be said, this is already too funny a mis-type.
-- Crutcher --
#include <disclaimer.h>
I am not arguing against free docs. I am arguing against the notion that those who produce books are evil.
-- Crutcher --
#include <disclaimer.h>
The whole promise of retinal scanning displays is that they are 1) incredibly sharp, and can (theoretically) 2) be squeezed into much small packages than LCD based systems (because LCD systems have to have an array /somewhere/ and RSD's don't.
/very/ interesting UI posibilities. Imagine themeable worlds in 20 years!)
True, this is currently only about the size of a normal LCD headset, but it will shrink, and I want one!!! (the little detail about see-through visual overlays has some
-- Crutcher --
#include <disclaimer.h>
Think of the sheer volume of time that must be spent creating the material for a course, then the additional volume of time that must be spent editing and verifying this material, and then the additional chunk that must be spent making sure that this is all taught in a consistent and flowing manner.
/well/ are usually found in seperate groups (programmers, editors, teachers); that each group's time is very valuable (in terms of average pay); and that individuals who fall far into multiple of these groups have an even /higher/ value placed upon their time.
Now, consider that individuals who have the skills to accomplish the first, second, and third tasks
People do the hard tech stuff, because it is fun. People write docs because they have to. People edit docs because they are paid to. Noone reorders docs for 'fun', 'cause it sucks, and they could be playing with code.
-- Crutcher --
#include <disclaimer.h>
Well, not really, but this is the basic solopsistic problem.
/without/ using your senses?
/probability/ of error.
Since your only interaction with the world is through your senses, how can you verify that it is as it seems, or even exists at all;
The best answer that anyone ever came up with is "I refute it thus" and kicking a rock. (not making this up). In reality, there is no true answer, indiviudals must make the "leap of faith", or the "leap of presumption" at least, and presume that the world is more or less as it appears to be.
Since true signatures validity can only be 'proven' by either A) testimony to the fact (which doesn't really require the signature, after the testimony) or B) the voice of 'experts'; the 'experts' can be cryptography experts, and can, like the hyndwriting experts, testify about the
And it is ultimately only about how probable it is, since you can't prove anything.
-- Crutcher --
#include <disclaimer.h>
Imageine:
The KDE League/GNOME Foundation crossover, where a portal is opened between two parallel developer communities so that they may avvert the Mighty Siesmic Network!
Preorders availbale now, comic on shelves June 2001.
-- Crutcher --
#include <disclaimer.h>
Note:
There is a large difference between voluntary categorization, which is the dewey deciaml system (voluntary by the library); the sections in bookstores (voluntary by the vendor) and MANDATORY labeling.
If you want to use pithy metaphores, its like saying, "You, you like brocoli, so you have to change your name to 'brocoli-lover' so that we can tell who you are", or "You're a jew, you have to wear this little star."
-- Crutcher --
#include <disclaimer.h>
You cannot establish a situation in which content must be labeled. It leads directly to censorship, period. Its ONLY purpose is censorship.
censorship is Baddddd, m'mkay?
Or did you miss out on that bit of history where the minority was crushed, oppressed, killed, and generally not treated very nicely by the majority?
Which bit is that? Why, its all points in time before this one.
-- Crutcher --
#include <disclaimer.h>
That slashdot editors dont actually read slashdot.
My proof? This article, which told about the development of this cool-ass tech months ago.
Vaporware? Can you pass the crack pipe? They've been working on this, and we've be reading about it, for some time.
This stuff is so cool, btw. Why use slow balistic calculations in games, when you've got enough space to store a lookup table! (Okay, that's rediculous, but this is still coolness)
-- Crutcher --
#include <disclaimer.h>
There are twqo basic types of clustering:
/is/ a valid answer, but it simplifies more than it educates.
1) Process clustering - This beowulf, it is designed to rip every last shred of CPU time out of boxen. It is a VERY custom, machine dependant thing. A good B-cluster will be so hand tweaked as to be almost unrecognizable as what ever distro.
2) Server clustering - this is failover stuff, and distros can do this much better. Most people call it something like High Availability. But you are still likely to teak it up.
This is not a very good question, because clusters tend to be so custom. Its like asking: "Whats the best frame to base a kit car on?" There
-- Crutcher --
#include <disclaimer.h>
Again, and again, and again,...
Whatever.
"Mr. Big Telco, I'd like to give you all this money to carry my traffic, but I guess you can't handle the routing anymore."
This is not a problem, this will not stop anything, solutions will be found, computers will be faster, memory will be cheaper.
-- Crutcher --
#include <disclaimer.h>
In my various English Lit. courses, the rule was always noted that one of the common word formation paths goes like this:
"foo bar" for a while,
then "foo-bar", when it becomes very common,
finally "foobar", when few can remember it as
the first, seperate words.
Seems about right,
"electronic mail"
"electronic-mail"
"e-mail"
"email"
Stop whinning.
-- Crutcher --
#include <disclaimer.h>
Really, no, I do. ...
'comon, man, act scared. I just told you I owned it. "I SEE ALL", see, didn't you here? You should give me money now
No, wait,
Hey KID!! stay away from that curtain, hey, HEY!!
Crap.
Please give me money anyway?
-- Crutcher --
#include <disclaimer.h>
Well, no, not really. /current/ competetors, but only to competetors during the period in question (when Linux most deffinately was NOT one)
Microsoft can't point to
-- Crutcher --
#include <disclaimer.h>
It does require registration, though there is an 'anonymous' registration option, that sends only your hardware archetecture (so that the right rpms get sent) and an email address. It is one of the free levels of service. (of which there are several)
-- Crutcher --
#include <disclaimer.h>
There is no distinction between 'official' and 'unofficial' ISO images. Its all the same ISO. And the daemon doesn't do anything unless you tell it to (but it is running).
The easyest fix is to just run up2date, and update the 'up2date' package, which owns the daemon.
-- Crutcher --
#include <disclaimer.h>
It damn well does what you tell it to. Linux is NOT CLI, linux is a kernel, and a pretty cool one at that.
And computers need kernels. Now, you can put any layer on top you want, and, BTW, GUI's ALWAYS need an extra layer (its just hidden from you sometimes).
-- Crutcher --
#include <disclaimer.h>