That's nothing. I used to have this little app for a Macintosh that would sing 99-bottles in a typical computerized voice. Funny part was you could enter any number you wanted in place of the 99. You wouldn't believe how funny it is hearing a tinny computer voice singing:
nine trillion, nine hundred ninety nine billion, nine hundred ninety nine million, nine hundred ninety nine thousand, nine hundred ninety nine bottles of beer on the wall. Take one down, pass it around, nine trillion, nine hundred ninety nine billion, nine hundred ninety nine million, nine hundred ninety nine thousand, nine hundred ninety eight bottles of beer...
wake me when its over.
Re:Backups, and being organized in a general way?
on
Database File System
·
· Score: 3, Insightful
Think of a directory structure as just one instance of a relational structure - a heirarchical or location-based one. Directories (or locations, or relationship to other files), even nested ones, are just another type of metadata. Once you have that concept in mind other things become obvious. For example you may group files by type (Image, Text) or by project, or by author. With a directory structure you either have to make multiple directories and symlink everything, or you're stuck with one view of your files.
In short it gives you multiple, simultaneous groupings of your data.
Golf: someone can hit you with a ball at close range. Tennis: The racket could snap and the sharp end could accidentally pierce your hide causing fatal blood loss. Swimming: Drowning, Chlorine poisoning, drowning.
All activities that you can pull a groin muscle doing too.
Yeah, it isn't. At best I guess as soon as you detect the eavesdropper you stop transmitting. (requires an ack/nak system) Then there is only a small amount of encrypted(?) data stolen that would not be sufficient(that word again) to be useful, or cracked. You'd still want to encrypt though.
PCI express is not just an AGP replacement. It is intended to completely replace PCI. PCI-X is/was a stopgap performance bump for those that needed it. PCI-e is the future.
EPS is PostScript. There are maybe a half dozen things that you can't do in EPS or must do that you otherwise have freedom to ignore in PS.
The problem with EPS as a file format is that it is too powerful. It is a language far more than it is a standard file format. To make a EPS importer you need a major chunk of code to parse all the possible EPS files that one could generate. You need a PostScript parser - a complete one. You just don't need the PS renderer. You need all the memory management and font handling.
I am not an SVG expert (I'm not sure I qualify as a PS expert either, but I work with it for a living), but I think it is much simpler in theory to implement one than a PS interpreter. Especially since the base language is XML and the parser for that already exists. I also believe that animations (automation?) in SVG is based on Javascript (and/or others?) so that already exists too.
Last, SVG has a nice structure. (E)PS is pretty damn free-form. Writiing tools to work with SVG without actually having to parse all of it is much easier than doing the same with EPS.
This Lawn Supervisor is working on a sprinkler maintenance job, when he starts working on a Findley Sprinkler head with a Langstrom 7 inch wrench.
Well his apprentice leans over and says "Hey, you can't work on a Findley Sprinkler head with a Langstrom 7 inch wrench!"
Well this infuriates the supervisor. So he grabs volume 14 of the Kingsley manual. Which says "The Langstrom 7 inch wrench can be used on the Findley Sprocket".
The apprentice retorts, "I says Sprocket, not Socket!"
Were those plumbers supposed to be here for _this_ show?
Slashdot Mirror
So, all we have to do is prove that the DMCA violates the DMCA and it will disappear in a puff of illogic, right?
Since they're all animals why not Mozilla Zoo (as compared with Mozilla Suite)?
That's nothing. I used to have this little app for a Macintosh that would sing 99-bottles in a typical computerized voice. Funny part was you could enter any number you wanted in place of the 99. You wouldn't believe how funny it is hearing a tinny computer voice singing:
nine trillion, nine hundred ninety nine billion, nine hundred ninety nine million, nine hundred ninety nine thousand, nine hundred ninety nine bottles of beer on the wall. Take one down, pass it around, nine trillion, nine hundred ninety nine billion, nine hundred ninety nine million, nine hundred ninety nine thousand, nine hundred ninety eight bottles of beer...
wake me when its over.
Think of a directory structure as just one instance of a relational structure - a heirarchical or location-based one. Directories (or locations, or relationship to other files), even nested ones, are just another type of metadata. Once you have that concept in mind other things become obvious. For example you may group files by type (Image, Text) or by project, or by author. With a directory structure you either have to make multiple directories and symlink everything, or you're stuck with one view of your files.
In short it gives you multiple, simultaneous groupings of your data.
Yes, yes, yes.
2) Add a history/revision list (DAV?).
Yeah, but who wants a monitor that keeps spitting grean soup at you and telling you that your mother is in there?
I'll keep my 16ms thank you.
Mechanical mouse with rubber ball that gets gummed up with dust and crud: $19.00
Optical mouse that doesn't work well on many surfaces: $39.00
Laser mouse that works on any surface and spawns lots of "frickin laser" jokes: Priceless.
See what I mean?
--
.sig?
The secret to getting modded up is to allways say i've got karma to burn in your sig..
Why would I say that You've got karma to burn in My
Oops. Damn, there goes the rest of my Karma.
Wrong story?
What's the Jolt! Cola of grammatical errors?
That would be MetaTalk.
Golf: someone can hit you with a ball at close range.
Tennis: The racket could snap and the sharp end could accidentally pierce your hide causing fatal blood loss.
Swimming: Drowning, Chlorine poisoning, drowning.
All activities that you can pull a groin muscle doing too.
Nah, you just have to be able to pull a groin muscle.
Shouldn't that be Maths ARE not a sport? No?, then maths is not a word. End of proof.
Flash must have been a bitch!
I thought it was a 12 minute powerbook. I think that is much more believeable.
Oh, I thought it was incryption when downloading and outcryption when uploading.
I got a bunch of code to go fix now...
Yeah, it isn't. At best I guess as soon as you detect the eavesdropper you stop transmitting. (requires an ack/nak system) Then there is only a small amount of encrypted(?) data stolen that would not be sufficient(that word again) to be useful, or cracked. You'd still want to encrypt though.
Don't you remember a few years ago, when the aliens came and destroyed Earth.
And we escaped to this planet on a giant Space Ark.
Then the Government decided not to tell the stupid people because they thought it might affect their memory.....
Um. Nevermind.
Bzzzttt. Thank you for playing.
PCI express is not just an AGP replacement. It is intended to completely replace PCI. PCI-X is/was a stopgap performance bump for those that needed it. PCI-e is the future.
Also, a lack of suction cups on my feet and hands.
No, saliva causes cancer.
But only when swallowed in small quantities, over a long period of time. - George Carlin
EPS is PostScript. There are maybe a half dozen things that you can't do in EPS or must do that you otherwise have freedom to ignore in PS.
The problem with EPS as a file format is that it is too powerful. It is a language far more than it is a standard file format. To make a EPS importer you need a major chunk of code to parse all the possible EPS files that one could generate. You need a PostScript parser - a complete one. You just don't need the PS renderer. You need all the memory management and font handling.
I am not an SVG expert (I'm not sure I qualify as a PS expert either, but I work with it for a living), but I think it is much simpler in theory to implement one than a PS interpreter. Especially since the base language is XML and the parser for that already exists. I also believe that animations (automation?) in SVG is based on Javascript (and/or others?) so that already exists too.
Last, SVG has a nice structure. (E)PS is pretty damn free-form. Writiing tools to work with SVG without actually having to parse all of it is much easier than doing the same with EPS.
This Lawn Supervisor is working on a sprinkler maintenance job, when he starts working on a Findley Sprinkler head with a Langstrom 7 inch wrench.
Well his apprentice leans over and says "Hey, you can't work on a Findley Sprinkler head with a Langstrom 7 inch wrench!"
Well this infuriates the supervisor. So he grabs volume 14 of the Kingsley manual. Which says "The Langstrom 7 inch wrench can be used on the Findley Sprocket".
The apprentice retorts, "I says Sprocket, not Socket!"
Were those plumbers supposed to be here for _this_ show?