Bill Gates said "OS/2 is the operating system of the future".
He would deny it, but the video of him saying it is all over the Internet.
I've been around long enough to know 2 things: "640K.." is likely true, and people like BG will deny it unless somebody can dig up a recording of it. Of course the quote itself would be from somewhere in about 1984(+/-)
I'm not hearing impaired but I'd like to add a comment or two. (Ok, sometimes my GF thinks I am...).
I worked in a lumber yard for about a year, this included driving a Forklift & using a saw all day so we had to wear hearing protection. I found it amazing how easy it was to adapt to the situation and learn to read lips in a general way. It was generally not too difficult to talk to people while standing beside a saw and talking to someone sitting on the runing forklift, and yet I found that quite difficult at first.
After a while it became second nature and I can't tell you whether I heard most of the conversation, or whether I lipread more than half of it.
Admitedly, not the same as someone who is left with lipreading or signlanguage.
I was thinking at first this was good advice, but actually, I don't think it is.
There is a significant likelyhood that the individual would slip into their old habbit of reading the subtitles without listening to the words. Never mind the movies where they don't even come close to matching.
Personally I think audio-books would be a good choice. It's a natural human voice, unlike a speech synthesizer. It will force the individual to listen as they don't have the words in front of them.
Of course, the best advice would probably be all of the above. Some of each, just don't slip into lazy habbits of reading instead of listening.
Actually, people do have similar problems: when they give other people their passwords.
Generally, passwords are a secret retained by the individual in limited quantities. It is not difficult for someone to remember wether or not they used upper case characters in their password. Typing passwords is partly about remember the letters in the password and partly about the motoskills to type the password. How many times have you realized you weren't sure of what letters were in your password, but knew if you had a keyboard in front of you you could type it.
The moment you start exchanging information with someone the issue of case sensitivity rears its ugly head. The moment you access a file you created 4 years ago the issue of case sensitivity rears its ugly head.
It isn't the file you accessed yesterday. Its the file you haven't accessed for 2 months. It's the file Joe own the hall sent you. Etc.
I'm not here to debate the issues related to other languages.
I'm saying that: For English usage differentiating between file.c and file.C is stupid.
case sensitivity isn't 'The Right thing.' it is an artifact of the times. Nothing more. I have absolutly no reason to believe it was an 'active' decision made the first time to be 'correct'. Rather it was 'it happened to work this way when we finished', or, 'well, it was faster than converting everything to uppercase for comparisons because we only had 2K of storage anyway.'.
I believe that case-sensitivity in a filesystem is nothing but a problem waiting to happen.
On the other hand, I used to program in C a lot and never had a major complaint about it being case sensitive. Of course I don't expect just anyone to be playing with C source code either.
The only reason why Unix is case sensitive is because it was easier, and faster to implement it as such in the early days.
It is not quite efficient to Preserve Case, and not make it case-sensitive.
I used a file system like this (HPFS) for many years and much prefer it over the case-sensitive alternatives.
It is also a security concern. If I have 2 files, which are identical except for case it is possible I could run the wrong one. Why? Point and Click interfaces barely show a difference between o and O, etc.
There is also no need for 2 files with the same name, and different case when it comes to SOURCE CODE. I have seen more than 1 program implemented like this and it is downright confusing and stupid. " No no, not "ubergeek.c", "Ubergeek.c"... etc.
Garbage. Crap. Total waste of resources.
I've been working in a database language that is case-insensitive for a number of years as well. It is damn nice to not have to worry about somebody typing something in differently than expected. It isn't a problem. And I don't have to call UPPER every time I do something!
While a similar, naturally occuring checmical exists doesn't mean a 'synthetic' is a good choice. (synthetic as in: Not naturally occuring in foods, used for some godawfull reason not having anything to do with good cooking).
By the way, for me, anything with MSG tastes like it has a 1/2lb of salt. Not kidding. 'course, to me pure, white sugar has a metallic flavour. Maybe I'm just strange.
On the other hand, naturally occuring forms in food don't bother me, or anyone I know.
Don't get me wrong here, I'm fully aware that 'I know people who get headaches' isn't scientific. I also know that MSG isn't usefull in good food under normal conditions.
But hey, you want to eat it, go ahead. Me, I'm not a fan.
I could care less about convincing you, if you are properly served by what you already have.
Me, cable isn't a choice, I'd be left with about 4 local stations that a hardly ever watch. And, once someone goes cable, around here the price difference is negligible (and, depending on options digital is slightly cheaper.).
My point was that the same level of functionality can exist without significant increase in cost.
You, currently, benefit from the fact that both your TV and your VCR have an analog tuner built in. In a few years it'll be a digital decoder instead. Right now the issue is the transition period.
And, admitedly, keeping the companies from screwing us over.
Note: I don't have to ever even see the second decoder box. It can be placed hidden in a cabinet. So, while it is an extra box/requirement it isn't a big deal either.
While I agree with you as to the actual effectiveness I don't think self-signing is actually a solution.
I know that Verisign is less than absolutly trust worthy. I also know they take atleast basic steps to ensure they issue a certificate to the correct entity. (Yes, they have made mistakes on that in the past, re: Microsoft).
I don't on the other hand, have any reason to believe you aren't a fly-by-night huckster waiting to receive a dozen (or thousand...) credit card numbers...
I want some level of assurance that you are indeed traceable. Even if, to some degree, its a false hope. Even if you pull off a scam on Verisign (or any other registrar) I know that there is a much larger trail to trace back to you and that it is more likely to get a good response from law enforcement authorities and/or financial institutions.
On the other hand, I've never concerned myself much with running programs which were self-signed. I mean, heck, I've run unknown programs on my computer since 1988, whats a few 'self-signed' programs...
There are a number of videos out there purporting to show things like this.
None of them are verifiable; all indications are that they are fake (some are), or, in some cases using the development SDK. Which makes it possible to run such programs on development X-boxes, but don't produce code which can legally be distributed. (As they require Microsoft libraries)).
Getting a non-Microsoft operating system on this machine to run with a minimum of hardware changes (preferably NONE) is the ultimate goal.
The best part? Its perfectly legal.
(I won't get into the Piracy aspects; but I personally find it interesting that games which can't be pirated (or, couldn't until very recently) are more expensive than games which can readily be pirated (almost anything for the PC). Only a few games for the PC have come out at the same pricepoint as the X-Box, or PS2 games. The other point: how the hell do you pirate an Xbox game cost effectly? Individually, you don't.)
Not all companies are like that. Maybe just the american ones??
I have 2 digital cable boxes for Shaw (Canada). The extra cost? None, except purchasing the box itself. (In my case free, as it was given to me by a friend).
There was no fee for enabling the second box, and no fee for continuing to use it. I -could- hook it up to my VCR and use it to record anything I want whenever I want. (VCR supports one of those ir-dongles to change cable box channels).
At one time I agreed with you, but, having used digital cable for a while I'm generally impressed with the implementation and attitude.
Yes, some shows are a little blocky, not compressed at the rate they should be, but most are fine. I've seen worse on analog cable as there are a couple of companies that get digital feeds and then broadcast them analog. (Worst of both worlds!).
The drive uses an extended function, often used on laptops, to not function fully until a passcode it sent to the drive. Once it is the drive acts normal.
As mentioned, this is the same as many laptop drives. Check out IBM and Toshiba's laptops with secure drives.
Slashdot Mirror
best date I could find for it was 1981.
So tell me, if it isn't on the net it didn't happen, right?
By the way, at the moment that BG said OS/2 is the os of the future Microsoft had already made high level descisions to push Windows and not OS/2.
Never trust BG, he's a businessman. Smart too.
But don't trust him.
According to your statements I should believe Bill Clinton never had sex with Lewinsky, right?
I mean, he denied it, and there aren't any recordings on the Internet...
Bill Gates said "OS/2 is the operating system of the future".
He would deny it, but the video of him saying it is all over the Internet.
I've been around long enough to know 2 things: "640K.." is likely true, and people like BG will deny it unless somebody can dig up a recording of it. Of course the quote itself would be from somewhere in about 1984(+/-)
I'm not hearing impaired but I'd like to add a comment or two. (Ok, sometimes my GF thinks I am...).
I worked in a lumber yard for about a year, this included driving a Forklift & using a saw all day so we had to wear hearing protection. I found it amazing how easy it was to adapt to the situation and learn to read lips in a general way. It was generally not too difficult to talk to people while standing beside a saw and talking to someone sitting on the runing forklift, and yet I found that quite difficult at first.
After a while it became second nature and I can't tell you whether I heard most of the conversation, or whether I lipread more than half of it.
Admitedly, not the same as someone who is left with lipreading or signlanguage.
I was thinking at first this was good advice, but actually, I don't think it is.
There is a significant likelyhood that the individual would slip into their old habbit of reading the subtitles without listening to the words. Never mind the movies where they don't even come close to matching.
Personally I think audio-books would be a good choice. It's a natural human voice, unlike a speech synthesizer. It will force the individual to listen as they don't have the words in front of them.
Of course, the best advice would probably be all of the above. Some of each, just don't slip into lazy habbits of reading instead of listening.
If I could run OS X on my current hardware I probably would.
Oh well... I liked BeOS too so what the hell do I know?
Actually, people do have similar problems: when they give other people their passwords.
Generally, passwords are a secret retained by the individual in limited quantities. It is not difficult for someone to remember wether or not they used upper case characters in their password. Typing passwords is partly about remember the letters in the password and partly about the motoskills to type the password. How many times have you realized you weren't sure of what letters were in your password, but knew if you had a keyboard in front of you you could type it.
The moment you start exchanging information with someone the issue of case sensitivity rears its ugly head. The moment you access a file you created 4 years ago the issue of case sensitivity rears its ugly head.
It isn't the file you accessed yesterday. Its the file you haven't accessed for 2 months. It's the file Joe own the hall sent you. Etc.
I'm not here to debate the issues related to other languages.
I'm saying that: For English usage differentiating between file.c and file.C is stupid.
case sensitivity isn't 'The Right thing.' it is an artifact of the times. Nothing more. I have absolutly no reason to believe it was an 'active' decision made the first time to be 'correct'. Rather it was 'it happened to work this way when we finished', or, 'well, it was faster than converting everything to uppercase for comparisons because we only had 2K of storage anyway.'.
I believe that case-sensitivity in a filesystem is nothing but a problem waiting to happen.
On the other hand, I used to program in C a lot and never had a major complaint about it being case sensitive. Of course I don't expect just anyone to be playing with C source code either.
It was definitly true on HP/UX version 9, probably 10 as well.
I ran into that problem more than once when users logged in with CAPS on...
Actually, according to what you've said files should be enforced to begin with a capital.
There is only 1 "Letter.txt". letter.txt would be generic, and not a noun, and therefor would have to be a folder.
oh god...
The only reason why Unix is case sensitive is because it was easier, and faster to implement it as such in the early days.
It is not quite efficient to Preserve Case, and not make it case-sensitive.
I used a file system like this (HPFS) for many years and much prefer it over the case-sensitive alternatives.
It is also a security concern. If I have 2 files, which are identical except for case it is possible I could run the wrong one. Why? Point and Click interfaces barely show a difference between o and O, etc.
There is also no need for 2 files with the same name, and different case when it comes to SOURCE CODE. I have seen more than 1 program implemented like this and it is downright confusing and stupid. " No no, not "ubergeek.c", "Ubergeek.c"... etc.
Garbage. Crap. Total waste of resources.
I've been working in a database language that is case-insensitive for a number of years as well. It is damn nice to not have to worry about somebody typing something in differently than expected. It isn't a problem. And I don't have to call UPPER every time I do something!
case-sensitive is a pain in the ass.
If, in 2 years, I can play a game that looks as good as Final Fantasy (the movie) I don't care how advanced rendering is for the movie industry.
I'd still be impressed by a 'movie' done with such a render.
The point to it is: there is not need to MSG.
While a similar, naturally occuring checmical exists doesn't mean a 'synthetic' is a good choice. (synthetic as in: Not naturally occuring in foods, used for some godawfull reason not having anything to do with good cooking).
By the way, for me, anything with MSG tastes like it has a 1/2lb of salt. Not kidding. 'course, to me pure, white sugar has a metallic flavour. Maybe I'm just strange.
On the other hand, naturally occuring forms in food don't bother me, or anyone I know.
Don't get me wrong here, I'm fully aware that 'I know people who get headaches' isn't scientific. I also know that MSG isn't usefull in good food under normal conditions.
But hey, you want to eat it, go ahead. Me, I'm not a fan.
I could care less about convincing you, if you are properly served by what you already have.
Me, cable isn't a choice, I'd be left with about 4 local stations that a hardly ever watch. And, once someone goes cable, around here the price difference is negligible (and, depending on options digital is slightly cheaper.).
My point was that the same level of functionality can exist without significant increase in cost.
You, currently, benefit from the fact that both your TV and your VCR have an analog tuner built in. In a few years it'll be a digital decoder instead. Right now the issue is the transition period.
And, admitedly, keeping the companies from screwing us over.
Note: I don't have to ever even see the second decoder box. It can be placed hidden in a cabinet. So, while it is an extra box/requirement it isn't a big deal either.
As someone who knows several people who get headaches from it I can tell you this: MSG is crap.
It serves no actual usefull purpose that cannot be found elsewhere. Its crap.
Only a bad Chinese resturaunt would use it.
It's crap.
It doesn't belong in food.
I'd like to change this a bit:
If your restricted by weight, what would you do?
(ie: the difference between camping, hiking, etc).
What are the most important tools? A camp stove, or a campfire... etc..
I second this. I was just thinking the same thing.
While I agree with you as to the actual effectiveness I don't think self-signing is actually a solution.
I know that Verisign is less than absolutly trust worthy. I also know they take atleast basic steps to ensure they issue a certificate to the correct entity. (Yes, they have made mistakes on that in the past, re: Microsoft).
I don't on the other hand, have any reason to believe you aren't a fly-by-night huckster waiting to receive a dozen (or thousand...) credit card numbers...
I want some level of assurance that you are indeed traceable. Even if, to some degree, its a false hope. Even if you pull off a scam on Verisign (or any other registrar) I know that there is a much larger trail to trace back to you and that it is more likely to get a good response from law enforcement authorities and/or financial institutions.
On the other hand, I've never concerned myself much with running programs which were self-signed. I mean, heck, I've run unknown programs on my computer since 1988, whats a few 'self-signed' programs...
Because Mozilla didn't handle it properly. It didn't fall for the trap, but it didn't notify the user in a usable manner that there was a problem.
So, it just looks like a bug.
There are a number of videos out there purporting to show things like this.
None of them are verifiable; all indications are that they are fake (some are), or, in some cases using the development SDK. Which makes it possible to run such programs on development X-boxes, but don't produce code which can legally be distributed. (As they require Microsoft libraries)).
Xbox is an early implementation of Paladium.
Getting a non-Microsoft operating system on this machine to run with a minimum of hardware changes (preferably NONE) is the ultimate goal.
The best part? Its perfectly legal.
(I won't get into the Piracy aspects; but I personally find it interesting that games which can't be pirated (or, couldn't until very recently) are more expensive than games which can readily be pirated (almost anything for the PC). Only a few games for the PC have come out at the same pricepoint as the X-Box, or PS2 games.
The other point: how the hell do you pirate an Xbox game cost effectly? Individually, you don't.)
Not all companies are like that. Maybe just the american ones??
I have 2 digital cable boxes for Shaw (Canada). The extra cost? None, except purchasing the box itself. (In my case free, as it was given to me by a friend).
There was no fee for enabling the second box, and no fee for continuing to use it. I -could- hook it up to my VCR and use it to record anything I want whenever I want. (VCR supports one of those ir-dongles to change cable box channels).
At one time I agreed with you, but, having used digital cable for a while I'm generally impressed with the implementation and attitude.
Yes, some shows are a little blocky, not compressed at the rate they should be, but most are fine. I've seen worse on analog cable as there are a couple of companies that get digital feeds and then broadcast them analog. (Worst of both worlds!).
The drive uses an extended function, often used on laptops, to not function fully until a passcode it sent to the drive. Once it is the drive acts normal.
As mentioned, this is the same as many laptop drives. Check out IBM and Toshiba's laptops with secure drives.
I upgraded my motherboard/processor. I went from a Pentium 200MMX to a Pentium III 500Mhz.
I had 3 operating systems installed.
Windows 95.
RedHat Linux.
BeOS.
Wanna guess which OS' ran immediatly without significant changes? yep. BeOS and Linux.
Both of them booted up fine the first time, (BeOS blew me away on that one. Very nice).
Windows95? Well, that took a long time to convince the system to quit trying to add new hardware after all the drivers were loaded/replaced etc.
The difference really was staggering.
Thats funny, I could do in BeOS 95% of what I do every day, the 5% I couldn't was work related.
Browse the net: No problem.
Watch TV in a window on the desktop: No problem.
Programming: No problem, heck of a Nice API too.
Heck, the TV functionality was added after I booted up with a new video card, installed the extra drivers necessary without rebooting. Sweet.
Actually, If I'm reading between the lines they will sell systems that don't have a Microsoft operating system (see nSeries)...
Any bets those systems will have a BIOS which will be configured upon sale to EITHER, run Windows, or NOW run windows....
So a system purchased with the future option to run windows must be puchased with a windows license on day one.