>Are you implying that Americans will just sit back and let that happen in the first place?
You mean, like the "sitting back and letting happen" that happened during the DMCA and stuff ?;-)
Funny I just like everyting with a good story.
on
Why Game Movies Stink
·
· Score: 1
And a lot of the people I know, also.
Wether that story is transmitted over a movie, a book, a computer game, or a pen and paper roleplaying sessions is not that important in my opinion.
... in the MS Office help as reference, I would estimate the service will sucessfull answer 0% of my questions.
The only way to find something there is via the keyword search. If it doesn't work on content where they have controll over the content, I can't imagine it working when they don't have controll over the content
And that's one of the reasons I don't have cell.;-)
The way it is now, even when the "normal" phone rings while I'm busy and don't expect some call I might not take it. If it was important, they will call again.
I agree on portability. I have a few cross-platform perl scripts that, depending on where they run, either use *.ini - files, environment variables or the registry to store configurations.
The bad thing about the registry is that it is never quite clear when and how it get's corrupted. We run a setup with about 30 terminalservers and roaming users, and some of those perl scripts I mentioned are used to write values into the user-registry that get lost or corrupted on a regular basis during login or logoff when it is transfered to or from the machine the user is logging on and the profile storage.
The concept of storing configuration in a database and not in a INI-file has advantages, but those advantages are mostly lost when it's a proprietary database that is stored on a fixed place. E.g. in our environment it would be better if we could put the user registries in a central database and get rid of the login/logoff corruption problems.
Hehehe... So any person finding it will think "Wow. that's interesting stuff. Let's dig further." ;-)
Contrary to popular believe and media hype Links != Porn. ;-)
I also regulary stumble over stuff at work while searching for programming / troubleshooting information that are send-home-worthy.
>Are you implying that Americans will just sit back and let that happen in the first place? You mean, like the "sitting back and letting happen" that happened during the DMCA and stuff ? ;-)
And a lot of the people I know, also.
Wether that story is transmitted over a movie, a book, a computer game, or a pen and paper roleplaying sessions is not that important in my opinion.
... in the MS Office help as reference, I would estimate the service will sucessfull answer 0% of my questions.
The only way to find something there is via the keyword search. If it doesn't work on content where they have controll over the content, I can't imagine it working when they don't have controll over the content
And that's one of the reasons I don't have cell. ;-)
The way it is now, even when the "normal" phone rings while I'm busy and don't expect some call I might not take it. If it was important, they will call again.
More of that "intelligent" pre-loading of programs and files. I want the OS to do what I WANT, not to do do what IT THINKS I WANT.
Well, don't be to hard on them. I can't read nor understand most licence agreements, too. At least not in the time I'm willing to invest into it. ;-)
Hmmm... Maybe I should check out this site, do 2 homeworks a day, quit my day job and party the rest of the time ?
I agree on portability. I have a few cross-platform perl scripts that, depending on where they run, either use *.ini - files, environment variables or the registry to store configurations.
The bad thing about the registry is that it is never quite clear when and how it get's corrupted. We run a setup with about 30 terminalservers and roaming users, and some of those perl scripts I mentioned are used to write values into the user-registry that get lost or corrupted on a regular basis during login or logoff when it is transfered to or from the machine the user is logging on and the profile storage.
The concept of storing configuration in a database and not in a INI-file has advantages, but those advantages are mostly lost when it's a proprietary database that is stored on a fixed place. E.g. in our environment it would be better if we could put the user registries in a central database and get rid of the login/logoff corruption problems.
... Now where have I heard somethig like that before ? ;-)
.... in their faces.
Founding of Microsoft : 1975
First documented use of smileys on electronic systems : 1972 or even earlier.
http://www.platopeople.com/emoticons.html