A Bad Week for Symantec
Evan Hughes writes "NeoSmart Technologies has published a scathing editorial regarding 3 high-profile mistakes by Symantec Corp. — all in less than a week. In what seems to be a string of stupid mistakes culminating in the infection of CNN-parent Turner Broadcasting Systems by Rinbot— a virus dedicated to the eradication of Symantec from the known world."
"KEEP the LAME shit on DIGG please!"
KEEP telling people of the SHAME called the BBC
0x2b || ~0x2b of course anyone can answer shakespears ultimate question with 0xFF
I have mod points and I am not afraid to use them
Oh yeah? Is that signed or unsigned 0xff?
:-)
Shakespeare's way ahead of you.
If moderation could change anything, it would be illegal.
anyone can answer shakespears ultimate question with 0xFF
;-)
I don't get it. What does End of File have to do with anything? To be, or not to be - end of file. Sounds lame and makes for a rather short play
Seven puppies were harmed during the making of this post.
No. They don't screw up on the hard facts. They screw up on details. In this case they didn't
get the timing right.
--"in this case someone at the BBC either heard something along the lines of along the lines
that build 7 is going to collapse and then accidentally had it reported as 'did collapse', or
maybe they just mixed up which buildings were gonna collapse."
Very funny. Actually this reminds me of the Bruce Willis movie where he plays a cop who catches
his best friend hiding in the closet in the bedroom. "No, no, it's alright, I know what happened,
it isn't your fault. You just tripped over the carpet here, stumbled, fell on my wife and your
dick just happened to go into her. It was an accident". (From what BW movie is that scene??)
Come on, you can make better excuses than that.
Unforunately that is 0x1 :( it should be:
0x2b | ~0x2b
and it will evaluate to 0xffff as a short, and 0xffffffff as a 32bit int/long
I fear the Y2038 bug