Well, as a matter of fact, I have read "From the Earth to the Moon", "20,000 Leagues Under the Sea", "War of the Worlds", and "The Time Machine". The timelessness of sci-fi is that we still *CAN* read these as works of literature even after enough hard scientific data exists to take them out of the realm of "speculative fiction." A good read is still a good read if you don't nitpick the technology/science.
And I might add, these books were eerily accurate in their speculations (with the exception of "War of the Worlds").
to be popular, or considered a classic, in 50 years is Nancy Collins's "Sonya Blue" trilogy about a vampire who is *not* undead. It was a damn fine read. Last time I saw it, it had been re-released in a single-volume trade paperback.
OTOH, control input is far less clear-cut. For example, moving files around directories will almost always be much faster using a GUI than a keyboard. Initial context setup takes some overhead (bringing up the source and destination folders), but after that, dragging files around with the mouse will beat the fastest touch typist every time, especially for longer file names.
Then again, this paradigm is poor for pattern selection. Moving random files around this way is faster, but moving all files containing the letters SSL will invariably be faster on the CLI.
The ideal is an intelligent blend of both.
Sounds almost like you're proposing an end to the "I'm more leet than you" religious wars...;-)
To be perfectly, honest, I feel the same way... if a GUI tool increases my communications bandwidth with the machine, I use it. If not, I use an xterm... after all, when you get to the bottom line, X was invented to allow an admin to have multiple terminals onscreen at once...
But for programming I use Xemacs... emacs, in general, has so many functions my muscle memory won't hold them all...
Where's the "ctrl" key? You already know exactly where it is.
Unless you admin an assortment of recent Sun boxen, where "ctrl" and "Caps Lock" are frequently interchanged, and the upper-right can be either the tilde or backspace. Keyboard shortcuts are WONDERFUL if you only work on one box, or if all the boxen come from a manufacturer who keeps things the same for more than six months at a time.
Well, DEC... oops... Compaq... oops, again... HP, and SGI as well, are all hanging in with Linux support/development/marketing projects, so I don't think I'm ready to pull the plug on Linux yet.
The ability to instantly cull photos that digital photography allows might just result in the loss of a significant portion of our pictorial history. Some of the greatest photojournalistic coups of all time were accidental... things caught in the background of a photo that were only discovered on later examination... many of these priceless records would have been lost if the pics they were found in could have been trashed instantly because "the light isn't right" or the composition sucks.
As for concern about digital-only storage, this concern is well-founded too. How do you recover the data when readers for the media are no longer available? Seen any 8" floppies lately? How about 5.25"? The cost of transferring terabytes of archives to new media has cost the loss of literally TONS of data. Film (preferably black and white, or separations on black and white film) is the ONLY suitable medium for archiving image data.
An easy way to calibrate the color and/or gray-scale response of a scanner ( or digicam ) is to go to your local high-end photo store ( one that deals in darkroom equipment ) and buy a color standard card. Kodak publishes them for use in calibrating color printing equipment and evaluating filter packs for color enlargers, and they are QUITE accurate. They also have a gray-scale reference card available. While this won't be as accurate as calibration against NIST primary standards, they don't cost as much either. These cards are NOT expensive, but the old, immutable rule is true. Cheap, fast, good... pick two. Do NOT use a laser printer for grey scale standards. Even inexpensive scanners can be set to use interpolated scanning at high enough resolution to resolve the toner particles.
As for x/y positional calibration, I made up a template for fret placement on a guitar fingerboard, once upon a time, by computing and plotting the fret placement in AutoCad and printing it out on a laser printer. The finished home-built instrument played scales more accurately in tune than my commercially-built acoustic guitar did. Or, if your school has a machinist on-campus, see if you can obtain a set of Jorgensen blocks and scan them. They are sized accurately to, IIRC, 0.0001 inch, or so. If you decide to use a laser printed calibration chart, be SURE you use a grid, rather than, say, a rectangle of a certain size. This way you will be able to determine whether there are any non-linearities in the motion of the scan head.
Accurate calibration standards just aren't THAT hard to find.
That's like breeding a chihuahua with a doberman. I don't know what will come out of such a union, and I doubt I want to...
You'll get either a small dog with a dobie attitude (bad news, but tolerable) or a BIG doc with a Chihuahua attitude (I'm not even sure THAT would be safe to live with)...;-)
While the Linux port is fairly recent, XFS (which supports ACLs in ways NTFS can only dream about) has been in use on production servers for almost 16 years. This would sort of indicate that the serious bugs are already out and any performance hits are a result of inappropriate use (XFS is optimizedfor HUGE database files) and/or incomplete optimization of the Linux port of XFS.
Actually, the prospect of not being able to sell to 20 + million AOL users is what will move websites back to standards compliance if AOL 7 is Gecko-based instead of IE-based.
This is not to say that 20 + million people can't be wrong. They do use AOL, after all. The message this comment is meant to convey is that 20 + million AOL members is a market force that must be considered in the decision-making process.
Want a great example? Captions of graphics being displayed in a box when you move the mouse pointer over them. This is a very system specific thing.
Funny, NS 4.77 on my Solaris box at work, AND on my Linux box at home, pops up tooltip-like boxes with whatever the content of the ALT parameter of the IMG SRC =... tag contains. Has for several back-level versions too.
Your opinion is all well and good until the owner of the site you develop for hires a vision-impaired person for a position requiring access to your pages.
In the U.S., at least, employers are required, by federal law, to make "reasonable accomodation" for their employees disabilities. For the visually-impaired, this usuallyhave seen one such person who used a systray-installed "display magnifier program.
My own opinion is that openness is the better path. My webpages may stike some as *BORRRRING* but they are best viewed with NS2 and above, IE 2 and above and/or Lynx. What I give up in neat tricks like pop-up menus, I try to make up for with meaningful content that can be read by all.
That's my $0.02. No one is responsible for my opinion but me, and sometimes I'm not responsible for it either.:-)
If I'd had points I'd have modded this up as "Interesting"... interesting that MSoft runs Windows Update on Java when they've taken Java out of XP... think we might see some thermonuclear consumer complaints from Joe Six-Pack when he tries to pick up SP1 in about 9 months? hehehehe
Frankly, AFAIC, MSN can lock out any browser they damned well please. I don't go to sites that require me to have a passport to receive anything but portal services.
I'll give my portal hits (and ad revenue) to Google, Yahoo, and excite!... but if THEY start requiring Passport, I might just start my own portal.
If it's a secure site, you don't trust the browser, you trust the certificate/public key YOU gave the browser.
Microsoft blocking Mozilla from MSN is just another case of "Damn you if you don't use Windows and IE... " which is what got them into anti-trust trouble in the first place.
IMHO, if you are sending personal e-mail of a sensitive nature over your employer's network, you are somewhere between an idiot and a fool on the intelligence scale. It's a well-established legal precedent that the network and ALL the data on it belong to the employer, and as a natural consequence, employees have NO right to privacy against employer snooping.
Actually, it took me one command (# apt-get install tcpdump) to install tcpdump, and about 10 minutes reading the man page to learn how to use it...
As for the next release, IIRC, the debian package has been updated about 5 times since I installed woody back in February, including minor version changes (i.e., it's not all package-tweaking noise).
The whole point of the project is NOT the data collection. If you had READ the site, the object of collecting the data is to use it as input to user-written clients for "artistic" visualization of chaotic data streams.
That doesn't change the fact that I, personally, think this falls in the category of YARBI (Yet Another REALLY Bad Idea(TM)).
The answer is they won't EVER sit in front of a Unix box until a prof requires them to for a class. Once that happens, those with an open mind will start going to the Unix boxen in preference to Windows for the same task. I've even seen students at Windows boxen fire up X-Win32 (great little X-client for Windows) when all the Unix machines were taken, but only after the initial shock wears off.
What was shocking to me about the Yorktown incident (thanks for the memory-jog there) was that they were using an Access database with a compiled VB client in a mission critical application, when it had been well-documented for years that a client crash would corrupt the database. I was also somewhat surprised that the crash of a database client was sufficient to take out vredir.dll, thus bringing down an entire network.
Slashdot Mirror
Well, as a matter of fact, I have read "From the Earth to the Moon", "20,000 Leagues Under the Sea", "War of the Worlds", and "The Time Machine". The timelessness of sci-fi is that we still *CAN* read these as works of literature even after enough hard scientific data exists to take them out of the realm of "speculative fiction." A good read is still a good read if you don't nitpick the technology/science.
And I might add, these books were eerily accurate in their speculations (with the exception of "War of the Worlds").
to be popular, or considered a classic, in 50 years is Nancy Collins's "Sonya Blue" trilogy about a vampire who is *not* undead. It was a damn fine read. Last time I saw it, it had been re-released in a single-volume trade paperback.
OTOH, control input is far less clear-cut. For example, moving files around directories will almost always be much faster using a GUI than a keyboard. Initial context setup takes some overhead (bringing up the source and destination folders), but after that, dragging files around with the mouse will beat the fastest touch typist every time, especially for longer file names.
... ;-)
... if a GUI tool increases my communications bandwidth with the machine, I use it. If not, I use an xterm ... after all, when you get to the bottom line, X was invented to allow an admin to have multiple terminals onscreen at once ...
... emacs, in general, has so many functions my muscle memory won't hold them all ...
Then again, this paradigm is poor for pattern selection. Moving random files around this way is faster, but moving all files containing the letters SSL will invariably be faster on the CLI.
The ideal is an intelligent blend of both.
Sounds almost like you're proposing an end to the "I'm more leet than you" religious wars
To be perfectly, honest, I feel the same way
But for programming I use Xemacs
Where's the "ctrl" key? You already know exactly where it is.
Unless you admin an assortment of recent Sun boxen, where "ctrl" and "Caps Lock" are frequently interchanged, and the upper-right can be either the tilde or backspace. Keyboard shortcuts are WONDERFUL if you only work on one box, or if all the boxen come from a manufacturer who keeps things the same for more than six months at a time.
Well, DEC ... oops ... Compaq ... oops, again ... HP, and SGI as well, are all hanging in with Linux support/development/marketing projects, so I don't think I'm ready to pull the plug on Linux yet.
The ability to instantly cull photos that digital photography allows might just result in the loss of a significant portion of our pictorial history. Some of the greatest photojournalistic coups of all time were accidental ... things caught in the background of a photo that were only discovered on later examination ... many of these priceless records would have been lost if the pics they were found in could have been trashed instantly because "the light isn't right" or the composition sucks.
As for concern about digital-only storage, this concern is well-founded too. How do you recover the data when readers for the media are no longer available? Seen any 8" floppies lately? How about 5.25"? The cost of transferring terabytes of archives to new media has cost the loss of literally TONS of data. Film (preferably black and white, or separations on black and white film) is the ONLY suitable medium for archiving image data.
An easy way to calibrate the color and/or gray-scale response of a scanner ( or digicam ) is to go to your local high-end photo store ( one that deals in darkroom equipment ) and buy a color standard card. Kodak publishes them for use in calibrating color printing equipment and evaluating filter packs for color enlargers, and they are QUITE accurate. They also have a gray-scale reference card available. While this won't be as accurate as calibration against NIST primary standards, they don't cost as much either. These cards are NOT expensive, but the old, immutable rule is true. Cheap, fast, good ... pick two. Do NOT use a laser printer for grey scale standards. Even inexpensive scanners can be set to use interpolated scanning at high enough resolution to resolve the toner particles.
As for x/y positional calibration, I made up a template for fret placement on a guitar fingerboard, once upon a time, by computing and plotting the fret placement in AutoCad and printing it out on a laser printer. The finished home-built instrument played scales more accurately in tune than my commercially-built acoustic guitar did. Or, if your school has a machinist on-campus, see if you can obtain a set of Jorgensen blocks and scan them. They are sized accurately to, IIRC, 0.0001 inch, or so. If you decide to use a laser printed calibration chart, be SURE you use a grid, rather than, say, a rectangle of a certain size. This way you will be able to determine whether there are any non-linearities in the motion of the scan head.
Accurate calibration standards just aren't THAT hard to find.
and I must say the side-by-side numbers make XFS look pretty good.
That's like breeding a chihuahua with a doberman. I don't know what will come out of such a union, and I doubt I want to...
... ;-)
You'll get either a small dog with a dobie attitude (bad news, but tolerable) or a BIG doc with a Chihuahua attitude (I'm not even sure THAT would be safe to live with)
#2 So what?
While the Linux port is fairly recent, XFS (which supports ACLs in ways NTFS can only dream about) has been in use on production servers for almost 16 years. This would sort of indicate that the serious bugs are already out and any performance hits are a result of inappropriate use (XFS is optimizedfor HUGE database files) and/or incomplete optimization of the Linux port of XFS.
Actually, the prospect of not being able to sell to 20 + million AOL users is what will move websites back to standards compliance if AOL 7 is Gecko-based instead of IE-based.
This is not to say that 20 + million people can't be wrong. They do use AOL, after all. The message this comment is meant to convey is that 20 + million AOL members is a market force that must be considered in the decision-making process.
Want a great example? Captions of graphics being displayed in a box when you move the mouse pointer over them. This is a very system specific thing.
... tag contains. Has for several back-level versions too.
Funny, NS 4.77 on my Solaris box at work, AND on my Linux box at home, pops up tooltip-like boxes with whatever the content of the ALT parameter of the IMG SRC =
Your opinion is all well and good until the owner of the site you develop for hires a vision-impaired person for a position requiring access to your pages.
:-)
In the U.S., at least, employers are required, by federal law, to make "reasonable accomodation" for their employees disabilities. For the visually-impaired, this usuallyhave seen one such person who used a systray-installed "display magnifier program.
My own opinion is that openness is the better path. My webpages may stike some as *BORRRRING* but they are best viewed with NS2 and above, IE 2 and above and/or Lynx. What I give up in neat tricks like pop-up menus, I try to make up for with meaningful content that can be read by all.
That's my $0.02. No one is responsible for my opinion but me, and sometimes I'm not responsible for it either.
If I'd had points I'd have modded this up as "Interesting" ... interesting that MSoft runs Windows Update on Java when they've taken Java out of XP ... think we might see some thermonuclear consumer complaints from Joe Six-Pack when he tries to pick up SP1 in about 9 months? hehehehe
Last I read, AOL had been kicked off the XP desktop ... wonder how that effects the contract ...
Javascript can be turned off.
... but if THEY start requiring Passport, I might just start my own portal.
Frankly, AFAIC, MSN can lock out any browser they damned well please. I don't go to sites that require me to have a passport to receive anything but portal services.
I'll give my portal hits (and ad revenue) to Google, Yahoo, and excite!
So, Your point is?
... " which is what got them into anti-trust trouble in the first place.
What webmaster NEEDS to trust a browser?
If it's a secure site, you don't trust the browser, you trust the certificate/public key YOU gave the browser.
Microsoft blocking Mozilla from MSN is just another case of "Damn you if you don't use Windows and IE
Well, then, I'd guess that your X-server is misconfigured, because X on my Linux box crashes so rarely that I can't remember when it happened.
IMHO, if you are sending personal e-mail of a sensitive nature over your employer's network, you are somewhere between an idiot and a fool on the intelligence scale. It's a well-established legal precedent that the network and ALL the data on it belong to the employer, and as a natural consequence, employees have NO right to privacy against employer snooping.
Actually, it took me one command (# apt-get install tcpdump) to install tcpdump, and about 10 minutes reading the man page to learn how to use it ...
As for the next release, IIRC, the debian package has been updated about 5 times since I installed woody back in February, including minor version changes (i.e., it's not all package-tweaking noise).
The whole point of the project is NOT the data collection. If you had READ the site, the object of collecting the data is to use it as input to user-written clients for "artistic" visualization of chaotic data streams.
That doesn't change the fact that I, personally, think this falls in the category of YARBI (Yet Another REALLY Bad Idea(TM)).
The answer is they won't EVER sit in front of a Unix box until a prof requires them to for a class. Once that happens, those with an open mind will start going to the Unix boxen in preference to Windows for the same task. I've even seen students at Windows boxen fire up X-Win32 (great little X-client for Windows) when all the Unix machines were taken, but only after the initial shock wears off.
Arrrgh! ... I even PREVIEWED and missed that screw-up
...
...
Open the file in notepad, hit <Ctl><End>
Ahhh, that's better
Well, let's see ... open the file in notepad, hit ... you're there ...
...
What *I* want to see someone do in Windows is the equivalent of 'tail -f mylogfile'
without using the cygwin GNU tools for Windows, that is>br>
What was shocking to me about the Yorktown incident (thanks for the memory-jog there) was that they were using an Access database with a compiled VB client in a mission critical application, when it had been well-documented for years that a client crash would corrupt the database. I was also somewhat surprised that the crash of a database client was sufficient to take out vredir.dll, thus bringing down an entire network.