Chances are, by the time this technology is ready for prime-time (if ever), chips will be utilizing vastly different technology than they are now.
Translation:
"By the time this slightly different technology is ready, it will be irrelevant because we'll already be using vastly different technology"
Of course! why didn't I think of that?
It's time to look to new technologies: carbon nanotubules and buckyballs, quantum computing, etc.
Isn't it lucky for us that these different technologies won't take nearly so long to develop!
After all, designing logic circuits from scratch with entirely new types of materials will be much faster than improving what already exists. And besides, using new materials will mean that none of the same design considerations come up. Or will it?
For example, try tracking the progress of a
long-lived pipe command. There's a LOT of value
to knowing whether you should sit and wait for a
command to finish, or if you should go read
slashdot for ten minutes while it's working.
So write an 'xpipe' application which executes a command pipe, and notifies you when each application exits, optionally with a popup message. Modify an existing shell to do this.
Pull your finger out man!
I just stick xclock at the end of a long pipeline,
so I can piss off and do something else.
Slashdot Mirror
Chances are, by the time this technology is ready for prime-time (if ever), chips will be utilizing vastly different technology than they are now.
Translation:
Of course! why didn't I think of that?
It's time to look to new technologies: carbon nanotubules and buckyballs, quantum computing, etc.
Isn't it lucky for us that these different technologies won't take nearly so long to develop!
After all, designing logic circuits from scratch with entirely new types of materials will be much faster than improving what already exists. And besides, using new materials will mean that none of the same design considerations come up.
Or will it?
For example, try tracking the progress of a long-lived pipe command. There's a LOT of value to knowing whether you should sit and wait for a command to finish, or if you should go read slashdot for ten minutes while it's working.
So write an 'xpipe' application which executes a command pipe, and notifies you when each application exits, optionally with a popup message. Modify an existing shell to do this.
Pull your finger out man!
I just stick xclock at the end of a long pipeline, so I can piss off and do something else.