The concept of adding self-contained "bricks" of hardware/software to build functionality in a system of devices sounds a lot like the goals of Sun's Jini project...
The whole point of the Internet is that people should be able to communicate without regard to what platform/software is being used. To do what this guy is doing actually improves MicroSoft's position, because it plays into their hands by turning the Internet into disconnected islands.
Actually, the whole point to RFCs is to standardize formats for things like mail headers. In this case, he is doing something that is perfectly within specs, n'est-ce pas? If so, by not following standards, it is Microsoft who is turning the Internet into disconnected islands (albeit one of those islands is VERY large and monopolistic).
If the bug doesn't appear on intel chips, then how are we supposed to believe that it's not an AMD bug?
Well, based on my reading of other posts, it is a simple case of AMD taking advantage of some features of AGP that are within spec that Intel is not. When the OS assumes that things are done Intel's way instead of adhering to the spec, things will show up on an AMD processor and not on an Intel.
AMD is doing things correctly, albeit differently from Intel. This is exactly how we are supposed to believe that it's not an AMD bug.
The reason we're often dependent on the name to determine the type of a file is that so far, it seems to be the only thing that really makes sense.
What about storing it externally the way Windows originally supported long filenames? Just use an external database to store information. The information would be stored when the file is created. (I'm not saying that Windows' way of supporting long filenames is perfect, but it was a decent hack/solution to solve it in an 8.3 world).
I believe that if you rename an RTF file so that it has the.DOC extension
I know this is kind of Off-Topic, but the question I have is this: WHY (oh why) are we so dependant on the file name!? Why don't we have a standard that says that the "header block" of a file determines its type. Why can't a ".txt" file be an executable? Just because the extension is different?? This is one of the legacies of DOS/Windows that I could really do without.
This was before any combat was supposed to have taken place. Excuse me for using the wrong Code Name.:-)
T
Re:You Believe This??
on
The Drone War
·
· Score: 2, Interesting
You are right... I met a guy about a week into Desert Storm... His arm was messed up... He said he got shot in Iraq.. before the war "started". He was home two weeks before it was official.
When there is no way to unsubscribe, or no way to contact because of forged headers then it becomes spam
Well, many spammers use the "click here to unsubscribe" link to verify that the email address is an active one (and thus be able to charge more to resell it in a SPAM list). I NEVER unsubscribe, because it just means more SPAM.
Have you ever used a calculator watch? They seem to hold up just fine. I don't really think it should be a challenge to make other stuff just as durable. It will take a few generations of the product to make it nice AND durable, but it shouldn't be hard for them to adapt from watches to other devices.
Slashdot Mirror
I don't see where there's a problem. It's all just code. It gets compiled. End of story.
T
T
It also sounds a lot like the Borg!
T
Actually, the whole point to RFCs is to standardize formats for things like mail headers. In this case, he is doing something that is perfectly within specs, n'est-ce pas?
If so, by not following standards, it is Microsoft who is turning the Internet into disconnected islands (albeit one of those islands is VERY large and monopolistic).
T
This is definitely coming off of existing cell phone towers. Those are very far apart (less maintenance costs, etc.)
T
T
Well, based on my reading of other posts, it is a simple case of AMD taking advantage of some features of AGP that are within spec that Intel is not. When the OS assumes that things are done Intel's way instead of adhering to the spec, things will show up on an AMD processor and not on an Intel.
AMD is doing things correctly, albeit differently from Intel. This is exactly how we are supposed to believe that it's not an AMD bug.
T
T
Caveat Emptor.
Get some mod points and mod me down if you like. It was what I understood the situation to be.
T
T
Ahh... always found that toolbar really annoying, so I don't show it :-) It's there. Thanks :-)
T
(Geez.. how many people just don't bother reading any articles before posting their "original idea"?)
T
T
Oh wait... COM+D monitors rock!
Wait... this is the last time, I promise: .NetD monitors kick ass!
T :-)
This certainly seems analogous to me. How can they justify this. It is effectively telling me what I'm allowed to do inside my own house!
That's crap.
T
Yeah... they just have that cute little frown face when something serious goes wrong (at least that's what the earlier Macs did)
T
What about storing it externally the way Windows originally supported long filenames? Just use an external database to store information. The information would be stored when the file is created. (I'm not saying that Windows' way of supporting long filenames is perfect, but it was a decent hack/solution to solve it in an 8.3 world).
T
I know this is kind of Off-Topic, but the question I have is this: WHY (oh why) are we so dependant on the file name!? Why don't we have a standard that says that the "header block" of a file determines its type. Why can't a ".txt" file be an executable? Just because the extension is different?? This is one of the legacies of DOS/Windows that I could really do without.
T
T
T
Do you find it as silly as I do to be called a "Diva" ?
Well, many spammers use the "click here to unsubscribe" link to verify that the email address is an active one (and thus be able to charge more to resell it in a SPAM list). I NEVER unsubscribe, because it just means more SPAM.
T
Have you ever used a calculator watch? They seem to hold up just fine. I don't really think it should be a challenge to make other stuff just as durable. It will take a few generations of the product to make it nice AND durable, but it shouldn't be hard for them to adapt from watches to other devices.
Man, This guy's gotta be old! I thought 8" floppies were as big as they got... But FIVE AND A QUARTER FEET! Holy Cow! ;-)