What is funny about this guy is that he has a blog that basically consists of a picture of him drinking beer and inane, banal comments about how well he slept last night (typical blog basically) then has the gall to put in all this crap about how it won't render properly in IE and I should upgrade to a standards compliant xhtml browser in order to read it properly! As if I give a s--t!
I once worked at a copy shop, and had to copy a couple of inches think program printout for some guy in a hurry in the middle of the night. It was a program to do credit scoring. In one part, there was a huge switch statement, based on the final score. If your score was really good, it printed something like "750+ Excellent". The last case statement was for something like 400 or less (presumably the programmer assumed this would never get hit), which said something like "You loser!! You have shitty credit and might as well crawl off and die!!". Even assuming that the user was not the person whose credit was being checked, I thought that was a good example of Unwise Programming Practices.
This isn't really possible because the message is sent to a lot of people at once by sending it to an alias. All the people get the same message because of the way email works. If they didn't see that the message hadn't also gone to a lot of other people, they wouldn't be so stupid as to leak it. So doing what you suggest would need someone with their fingers in the guts of the email server...
Huh? The major Microsoft products are localized into different flavors of English. For example, if you buy Windows in the UK it will ask whether you want 32-bit "colour". Some of the less big selling products are only localized into US English. And even in Windows, some spellings are sometimes left the same if they are a trademark (I think "network neighborhood" may be one). But in general, Microsoft has some of the best localization around. You don't know what you're missing.
Typically the Microsoft folks in Redmond are responsible for three localized versions: English, German, and Japanese. That doesn't mean they actually do the localization, but they are not deemed to have fully shipped until those three are tested. Other locales are the responsibility of different groups. The reasoning is that German and Japanese localization catches 80%+ of internationalization bugs: mainly long word length and high ascii (German) and unicode, input method editors, and different script orientation (Japanese). Of course locales like Arabic and Hebrew find more possible bugs too, but those three catch most of them.
This is bad advice. The RAM drive may well get paged to disk. Also any processing on it may well involve temp files on disk. It's pretty hard to think of useful things you can do with sensitive data that never involve putting anything sensitive on disk.
If I remember quickly, after Saigon fell, the Vietnamese reconstructed a bunch of embarrassing documents that had been left in the US Embassy in the rush to depart. They had been shredded, but (if I recall correctly from the film of it) only in one dimension. The Vietnamese had no shortage of manpower or motivation, and stuck all the bits together.
I should think the same is theoretically possible for many of the cheaper 2D shredders. The problem (if you had the patience) would be that the bits are so small, the slightest draft would ruin everything.
This is just a troll..NET apps run in a configurable security sandbox, and use runtime type checking. How often does your Java code suffer from a buffer overrun?
Slashdot Mirror
What is funny about this guy is that he has a blog that basically consists of a picture of him drinking beer and inane, banal comments about how well he slept last night (typical blog basically) then has the gall to put in all this crap about how it won't render properly in IE and I should upgrade to a standards compliant xhtml browser in order to read it properly! As if I give a s--t!
I once worked at a copy shop, and had to copy a couple of inches think program printout for some guy in a hurry in the middle of the night. It was a program to do credit scoring. In one part, there was a huge switch statement, based on the final score. If your score was really good, it printed something like "750+ Excellent". The last case statement was for something like 400 or less (presumably the programmer assumed this would never get hit), which said something like "You loser!! You have shitty credit and might as well crawl off and die!!". Even assuming that the user was not the person whose credit was being checked, I thought that was a good example of Unwise Programming Practices.
This isn't really possible because the message is sent to a lot of people at once by sending it to an alias. All the people get the same message because of the way email works. If they didn't see that the message hadn't also gone to a lot of other people, they wouldn't be so stupid as to leak it. So doing what you suggest would need someone with their fingers in the guts of the email server ...
Huh? The major Microsoft products are localized into different flavors of English. For example, if you buy Windows in the UK it will ask whether you want 32-bit "colour". Some of the less big selling products are only localized into US English. And even in Windows, some spellings are sometimes left the same if they are a trademark (I think "network neighborhood" may be one). But in general, Microsoft has some of the best localization around. You don't know what you're missing.
Typically the Microsoft folks in Redmond are responsible for three localized versions: English, German, and Japanese. That doesn't mean they actually do the localization, but they are not deemed to have fully shipped until those three are tested. Other locales are the responsibility of different groups. The reasoning is that German and Japanese localization catches 80%+ of internationalization bugs: mainly long word length and high ascii (German) and unicode, input method editors, and different script orientation (Japanese). Of course locales like Arabic and Hebrew find more possible bugs too, but those three catch most of them.
This is bad advice. The RAM drive may well get paged to disk. Also any processing on it may well involve temp files on disk. It's pretty hard to think of useful things you can do with sensitive data that never involve putting anything sensitive on disk.
How else are you supposed to dispose of your severed limbs and torsos, brainiac? Eh?
Personally, whenever my bare-chested friends help me move large appliances, I make sure I destroy all the photos afterwards.
E X A C T L Y
If I remember quickly, after Saigon fell, the Vietnamese reconstructed a bunch of embarrassing documents that had been left in the US Embassy in the rush to depart. They had been shredded, but (if I recall correctly from the film of it) only in one dimension. The Vietnamese had no shortage of manpower or motivation, and stuck all the bits together. I should think the same is theoretically possible for many of the cheaper 2D shredders. The problem (if you had the patience) would be that the bits are so small, the slightest draft would ruin everything.
What major component of the OS was Linux's innovation? All popular computer systems are heavily derivative of each other. So what?
In the majority of software projects, ease of development and maintenance is many times more significant than speed of program execution.
This is just a troll. .NET apps run in a configurable security sandbox, and use runtime type checking. How often does your Java code suffer from a buffer overrun?
That site is overloaded. Try this one. This track is particularly bad: aaargh
Your proof?
You realize you can get XP to run with the Win2000 interface? You idiot!
They get detention?