There is hardly any need to crash it. Just put it in a low Jovian orbit underneath all the moons. From there it wouldn't have the energy necessary to climb back up to where the moons are.
keyboarding, not PCs, should be the required skill
on
Laptops In Education
·
· Score: 1
What's needed is a mandatory typing class for all, middle school at the latest. I've never understood why, with today's emphasis on computers, keyboarding skills get short shrift in our educational system.
Re:Should we be celebrating hoax's?
on
Hoax-a-go-go!
·
· Score: 1
I don't really think we should be celebrating hoax's as funny points of amusement.
Sorry, I have to disagree. Humor has always been the best way to defuse anything.
4. they get bored with that piece of code they developed. How many years can any person look at one piece of code anyways before needing a new challenge?
5. they acquire a family they have to feed with littl'uns that have to be sent to college. There goes that bohemian worry-only-about-me lifestyle.
At my own place of employment we have two out-of-state telecommuters, one in Ohio and the other in Colorado. Both were normal employees for a substantial period of time, before they had to move for family reasons. From what I can see, having that face-to-face period with colleagues and bosses before becoming a telecommuter establishes you as a real person in their minds which increases the chance of success of the telecommuting arrangement.
At home I use my old HDs as backup devices. What I like best about this is the random-access nature of old-file retrieval and viewing one gets from using a disk as a backup.
Plan 9 from Bell Labs had an interesting backup system that I've never seen elsewhere. They backed up to a CDRW-farm every night that had storage capacity for 3 years of nightly backups. It didn't use as much space as one would think since they employed a custom backup filesystem that reused storage when a file hadn't changed from one night to the next. The beauty of this system was its ease of perusual and restoration of files. The nightly backup was an exact image that one could cd into, just like for a normal disk based filesystem. Everything, of course, was read-only, even if the write-permission bit was set.
The IDE interface has only enough wires for 256GB. This disk is interesting in that at 75GB we are getting within shouting distance of this hard limit. Perhaps in the future all disks will be SCSI. Or perhaps we will go to a block size larger than 512bytes. Or maybe we will even add more wires to the IDE interface, or multiplex the existing wires more efficiently.
"The PTO is not yet equipped to handle general email correspondence. General inquires should be made by hand-cranked telephone on in longhand on parchment to one of the addresses specified in the PTO directory. This directory may be found on stone tablets buried somewhere in the sands of the Egyptian desert.
Ksh always has had readline support. I believe Korn invented the concept. Just set the environment variable EDITOR to vi or emacs to get the desired personality.
For a time. early to mid 20th-century, acid-free paper was noticably more expensive so there was a tendency not to use it. However its price has come down so now most printing use it. Here are some statistics from a published source:
Of all the new acquisitions tested, 89% were printed on acid-free paper. Approval orders--books arriving as part of a vendor selection plan--were printed on acid-free paper 97% of the time. Only 1% of hardcover approval orders were acidic. Compare this with 30% of softcover approval orders and the difference is marked. Of firm orders--orders placed by the library to a vendor or publishing house--82% were acid-free. Hardcover books (which accounted for 70% of the firm orders) were 93% acid-free while 80% of the softcover were printed on acid-free stock.
WAP is parallel with and incompatible to HTTP/TCP/IP. It's only advantage is that it is optimized for 1) low bandwidth and 2) low resolution display devices. High bandwidth wireless connections eliminate the need for 1). The natural growth in power of handhelds over time (Transmeta is the next step in this progression) means 2) can be done in the handheld rather than in the WAP server.
You're missing the point. With high bandwidth, there's no reason wireless web browsing shouldn't be anything other than HTTP over TCP/IP.. just like the wired desktop is today. No one is arguing that wireless is unimportant. Of course it is important and is the future. It just won't be WAP.
The article's premise is wrong. A game programmer isn't the equivalent of a movie industry star. S/he's the equivalent of a grip or at most a set designer.
It's pretty bad that you just can't tell anymore whether this is a result of incompetence or a deliberate move...
[I know, this is slightly off subject] It's both. Putting out a marginal, barely working product is what happens naturally to any piece of software if special, talented care isn't put in from the first to keep that from happening. No malicious, direct action is necessary. It is the default result.
Then, after putting out a marginal product, a company gets rewarded by its customers. They are eager to buy the next release, in order to get bug fixes and design fixes, the latter otherwise known as `new features'. They are eager to buy the company's books in order to learn how to use the obfuscated product. And they are eager to sign up for the company's support, consulting, and training services necessary to keep it running. With these benefits, a software company has little incentive to put in the (tremendous) effort to reorganize itself so that the above default result doesn't happen.
Someday, software customers, like those of other industries, may wise up and simply stop buying shoddy software. Perhaps in a few decades.
Although Ghostscript may be a mess, but I've never had any trouble doing single-sheet, hand-feed double sided printing, or envelope feeding with my printer. I pop out the paper tray so it can't be found, then feed manually though the dedicated manual slot (HP LaserJet 5P).
You are making things too complicated. The article's main complaint is that too many admins have not set up password protection on their SQL servers. This is negligence of the first order. Your long series of second-order security precautions comes into play only after the competence of these admins rises to the point where they see the need and can do password assignment. And that won't happen universally, across the board, until corporations become liable for this sort of negligence [IANAL, so they may already be liable for this and we are only waiting for a test case to prove it].
My own, private worry over Mozilla is that it renders pages way too slow on my steadfast & sturdy 120MHz system. The artifacts produced when resizing, uncovering, etc are really quite visually distressing. For this reason alone I won't be using Mozilla as my primary browser.
Re:Design of Mozilla must address fears of busines
on
Mozilla Status Update
·
· Score: 2
A site that `filters out browsers' is being unnecessarily aggressive against their own customers. It is difficult to stay in business when constantly telling your customer to shove it.
Perhaps you should try writing your web pages more conservatively? The best pages don't use java or javascript much anyways. That is, if one doesn't consider `the carnival experience' as a critera for being a good web page.
This is true; however, the course-grained semaphoring in Linux is at this very moment rapidly being replaced with fine-grained semaphoring. When this is complete Linux likely may start beating NT in the large-cpu configurations.
Slashdot Mirror
There is hardly any need to crash it. Just put it in a low Jovian orbit underneath all the moons. From there it wouldn't have the energy necessary to climb back up to where the moons are.
And don't forget the monitor ($150), keyboard ($30) and mouse ($25). And speakers for that sound card. A floppy ($20) would be nice to have too.
The new slashdot server appears to be slashdotted...
Piranha is a good name for this module.
What's needed is a mandatory typing class for all, middle school at the latest. I've never understood why, with today's emphasis on computers, keyboarding skills get short shrift in our educational system.
Sorry, I have to disagree. Humor has always been the best way to defuse anything.
Perhaps you should add....
4. they get bored with that piece of code they developed. How many years can any person look at one piece of code anyways before needing a new challenge?
5. they acquire a family they have to feed with littl'uns that have to be sent to college. There goes that bohemian worry-only-about-me lifestyle.
At my own place of employment we have two out-of-state telecommuters, one in Ohio and the other in Colorado. Both were normal employees for a substantial period of time, before they had to move for family reasons. From what I can see, having that face-to-face period with colleagues and bosses before becoming a telecommuter establishes you as a real person in their minds which increases the chance of success of the telecommuting arrangement.
At home I use my old HDs as backup devices. What I like best about this is the random-access nature of old-file retrieval and viewing one gets from using a disk as a backup.
Plan 9 from Bell Labs had an interesting backup system that I've never seen elsewhere. They backed up to a CDRW-farm every night that had storage capacity for 3 years of nightly backups. It didn't use as much space as one would think since they employed a custom backup filesystem that reused storage when a file hadn't changed from one night to the next. The beauty of this system was its ease of perusual and restoration of files. The nightly backup was an exact image that one could cd into, just like for a normal disk based filesystem. Everything, of course, was read-only, even if the write-permission bit was set.
The IDE interface has only enough wires for 256GB. This disk is interesting in that at 75GB we are getting within shouting distance of this hard limit. Perhaps in the future all disks will be SCSI. Or perhaps we will go to a block size larger than 512bytes. Or maybe we will even add more wires to the IDE interface, or multiplex the existing wires more efficiently.
"The PTO is not yet equipped to handle general email correspondence. General inquires should be made by hand-cranked telephone on in longhand on parchment to one of the addresses specified in the PTO directory. This directory may be found on stone tablets buried somewhere in the sands of the Egyptian desert.
As a /. reader service: of the dozen or so that I read at random, 12 was the most persuasive. 235 and 36 were also thought provoking.
Ksh always has had readline support. I believe Korn invented the concept. Just set the environment variable EDITOR to vi or emacs to get the desired personality.
WAP is parallel with and incompatible to HTTP/TCP/IP. It's only advantage is that it is optimized for 1) low bandwidth and 2) low resolution display devices. High bandwidth wireless connections eliminate the need for 1). The natural growth in power of handhelds over time (Transmeta is the next step in this progression) means 2) can be done in the handheld rather than in the WAP server.
You're missing the point. With high bandwidth, there's no reason wireless web browsing shouldn't be anything other than HTTP over TCP/IP .. just like the wired desktop is today. No one is arguing that wireless is unimportant. Of course it is important and is the future. It just won't be WAP.
Ahhhhhh finally, high bandless wireless. This should kill WAP, if the WAP patentsquatting fiasco doesn't kill it first.
The article's premise is wrong. A game programmer isn't the equivalent of a movie industry star. S/he's the equivalent of a grip or at most a set designer.
Then, after putting out a marginal product, a company gets rewarded by its customers. They are eager to buy the next release, in order to get bug fixes and design fixes, the latter otherwise known as `new features'. They are eager to buy the company's books in order to learn how to use the obfuscated product. And they are eager to sign up for the company's support, consulting, and training services necessary to keep it running. With these benefits, a software company has little incentive to put in the (tremendous) effort to reorganize itself so that the above default result doesn't happen.
Someday, software customers, like those of other industries, may wise up and simply stop buying shoddy software. Perhaps in a few decades.
The XML FAQ is here.
Although Ghostscript may be a mess, but I've never had any trouble doing single-sheet, hand-feed double sided printing, or envelope feeding with my printer. I pop out the paper tray so it can't be found, then feed manually though the dedicated manual slot (HP LaserJet 5P).
Maybe other printers forbid this option though.
You are making things too complicated. The article's main complaint is that too many admins have not set up password protection on their SQL servers. This is negligence of the first order. Your long series of second-order security precautions comes into play only after the competence of these admins rises to the point where they see the need and can do password assignment. And that won't happen universally, across the board, until corporations become liable for this sort of negligence [IANAL, so they may already be liable for this and we are only waiting for a test case to prove it].
My own, private worry over Mozilla is that it renders pages way too slow on my steadfast & sturdy 120MHz system. The artifacts produced when resizing, uncovering, etc are really quite visually distressing. For this reason alone I won't be using Mozilla as my primary browser.
A site that `filters out browsers' is being unnecessarily aggressive against their own customers. It is difficult to stay in business when constantly telling your customer to shove it.
Perhaps you should try writing your web pages more conservatively? The best pages don't use java or javascript much anyways. That is, if one doesn't consider `the carnival experience' as a critera for being a good web page.
This is true; however, the course-grained semaphoring in Linux is at this very moment rapidly being replaced with fine-grained semaphoring. When this is complete Linux likely may start beating NT in the large-cpu configurations.