I wonder if TFA has actually measured that disk swapping happens (easy with procexp or perfmon), or are just shouting their heads off without understanding what's going on...
Agreed. In fact, when I first created a gravatar, this "newly discovered" problem immediately occurred to me; I suspect the same is true for many other gravatar users.
Granted, those are basically very unsophisticated databases that just store lookup values, but it's relatively easy to bruteforce an MD5 hash down into one of the possible original strings
No, it's not. Or at least, it only is if you have truly awesome amounts of time or computing resources to spend. Hence lookup databases like those you reference.
That's exactly the source of bugs. Typing out by hand a long descriptive name will either be correct or (in a decent language) a compile error.
Using autocomplete allows you to get the wrong variable without noticing, and doesn't always get a compile error.
(Nevertheless, descriptive variable names are well worth it.)
That doesn't seem to be the case here; s is a "source", s->ss is the source's list of "sub-sources". So the s and ss names are just accurate abbreviations, not an example of your "x" and "xx" phenomenon. The "next" pointer for a sub-source itself being named "ss" is a little strange though.
Without giving MS a chance to fix it? If they had someone with half a brain making the decisions, they would never have used a tracking pixel like that - it's just plain broken by design.
And I bet the MS engineers who worked on this said so and were ignored.
I don't get it; doesn't everyone use quotes from songs, literature, or film in their code? "I always have a quotation for everything - it saves original thinking."
Slashdot Mirror
Pity twitter doesn't use Perl, which has its very own utf8 encoding that supports 72 bits per character.
I wonder if TFA has actually measured that disk swapping happens (easy with procexp or perfmon), or are just shouting their heads off without understanding what's going on...
I give you one guess.
I thought that was a really slick marketing twist on someone's part.
r
Um, no, he didn't. That was the original joke, just using subtlety instead of the ice pick to the forehead.
right over your head
Very odd off-by-one?
*cough* Lingua::EN::Inflect *cough*
Hence the smiley. I won't go along with you in labeling indigenous Australians as all "ne'er-do-wells", though.
There, they want to censor everyone; the UK proposal would only be used against bad guys. :)
Agreed. In fact, when I first created a gravatar, this "newly discovered" problem immediately occurred to me; I suspect the same is true for many other gravatar users.
I disagree.
Granted, those are basically very unsophisticated databases that just store lookup values, but it's relatively easy to bruteforce an MD5 hash down into one of the possible original strings
No, it's not. Or at least, it only is if you have truly awesome amounts of time or computing resources to spend. Hence lookup databases like those you reference.
I don't see Mr. Perens anywhere saying anything about wanting a different license. Care to provide a link or at least a quote?
But you see no difference between socialism and capitalism? Your "knowing jack" doesn't seem a high threshold.
I don't know why, but I read the story title as "Palin Sued Over Palm Pre GPL Violation".
CERN recently invoked the curse too: http://press.web.cern.ch/press/PressReleases/Releases2009/PR18.09E.html.
Don't include Perl in that list, unless you mean non-strict script-kiddie Perl.
That's exactly the source of bugs. Typing out by hand a long descriptive name will either be correct or (in a decent language) a compile error. Using autocomplete allows you to get the wrong variable without noticing, and doesn't always get a compile error.
(Nevertheless, descriptive variable names are well worth it.)
That doesn't seem to be the case here; s is a "source", s->ss is the source's list of "sub-sources". So the s and ss names are just accurate abbreviations, not an example of your "x" and "xx" phenomenon. The "next" pointer for a sub-source itself being named "ss" is a little strange though.
"An Inconvienient Place: About 70 Miles East of Here, Where It's Lighter"
And I bet the MS engineers who worked on this said so and were ignored.
Nothing is as bad as dried ramen sauce
Makes me think of proof glass or wardable paint from http://www.amazon.com/Sunshine-Robin-McKinley/dp/0425191788 I guess truth really is at least as strange as fiction.
I don't get it; doesn't everyone use quotes from songs, literature, or film in their code? "I always have a quotation for everything - it saves original thinking."
Microsoft takes backwards compatibility very seriously.
How seriously? 1.#INF seriously.