while(1) {
fprintf(stdout, "New IE Vulnerability puts Windows users at risk!");
sleep 86400;
fprintf(stdout, "New Firefox Vulnerability, is Firefox as secure as it say?");
sleep 86400; }
Years ago when I first brought in my G4 Powerbook into the office, most people had no idea what Mac OSX or any concrete reason to switch... but withtin 2 weeks five of my cubemates did. You know why? Because it was pretty. Guess what else? Four of them switched back because of various incompatibilities with how they used to use their Windows-based computers.
People are sheep.
Vista is all Microsoft. The product as a whole shares direction and intercommunication. The flavors are essentially nothing more than marketing.
Linux distros on the otherhand are for the most part completely independent of one another. Each of them going off in their own direction without any thought as to what the other is doing and almost zero collaboration.
I wonder what the Linux community could do if they focused their attention on a single platform/architecture.
The simple fact is, most programmers, just like every other industry are just that, 'average'. You look around and 90% of the workforce wouldn't spend more than a second considering picking up a book or otherwise researching new emerging technologies. They just sit there waiting to be told what to do. Sheep.
If you're ambitious, specialized and good at what you do, money is easy and you'll make a hell of a lot more than the 'average'.
Google Talk comes out with Beta 1 and gets nothing but praise enough though it has 1/10th the functionality of other IM offerings.. but hey, it's *******OPEN******* (sort of).
MS comes out with Beta 1 of Vista and IE7 and gets nothing but bitch slaps for more than anything, because it's MS. Forget cool features like anti-phishing in IE7.
Lets step back here and look at Tiger Beta 1... it crashed only a daily basis and had very limited new functionality. It was nothing like the final release. Yet here we're comparing Tiger release to Vista Beta 1....
Anyways, like Apple, I'm sure MS has quite a few tricks up their sleaves which we haven't seen in Vista B1.
The simple fact is that recruiters and HR folks look for keywords. Certification acronyms are a major part of them.
While they hold no real technical merit, non-technical employees/companies don't know that.
I really don't understand where you're going with DCC... What does the fact the two DCC/IRC clients communicate with eachother directly have to do with anything?
Are you saying that if they aren't proxying through a 3rd party that there's no other factors to consider when identifying the source of latency?
Slashdot Mirror
The Slashdot userbase isn't indicative of the general public. They tend to smell worse, and view patching Firefox as a fun and rewarding hobby.
while(1)
{
fprintf(stdout, "New IE Vulnerability puts Windows users at risk!");
sleep 86400;
fprintf(stdout, "New Firefox Vulnerability, is Firefox as secure as it say?");
sleep 86400;
}
Years ago when I first brought in my G4 Powerbook into the office, most people had no idea what Mac OSX or any concrete reason to switch... but withtin 2 weeks five of my cubemates did. You know why? Because it was pretty. Guess what else? Four of them switched back because of various incompatibilities with how they used to use their Windows-based computers. People are sheep.
Here:
Firefox 1.x 2005
IE 6.x 2005
Not really an accurate comparison.
Vista is all Microsoft. The product as a whole shares direction and intercommunication. The flavors are essentially nothing more than marketing.
Linux distros on the otherhand are for the most part completely independent of one another. Each of them going off in their own direction without any thought as to what the other is doing and almost zero collaboration.
I wonder what the Linux community could do if they focused their attention on a single platform/architecture.
You're an idiot who's spreading misinformation.
http://www.frsirt.com/english/advisories/2005/1690
Affected Products:
Mozilla Firefox version 1.0.6 and prior
Mozilla Firefox version 1.5 Beta 1 and prior
Mozilla Suite version 1.7.11 and prior
Not "may", "does". It's a remotely exploitable vul in Netscape and Firefox.. Plain and simple.
The simple fact is, most programmers, just like every other industry are just that, 'average'. You look around and 90% of the workforce wouldn't spend more than a second considering picking up a book or otherwise researching new emerging technologies. They just sit there waiting to be told what to do. Sheep.
If you're ambitious, specialized and good at what you do, money is easy and you'll make a hell of a lot more than the 'average'.
Good point.
I can't wait to see what kind of negative spin Slashdot will put on this.
"Mazda Switches To USB Keys" - Seems pretty misleading to me. Perhaps, "Mazda considers switching to USB keys"?
90% of that car will change before production.
Yeah, and IBM has no interest in Linux having a lower TCO. :)
I bet you got a lot of good information working on the helpdesk.
Come on now, that's ridiculous. It might as well be 10 years.
Google Talk comes out with Beta 1 and gets nothing but praise enough though it has 1/10th the functionality of other IM offerings.. but hey, it's *******OPEN******* (sort of). MS comes out with Beta 1 of Vista and IE7 and gets nothing but bitch slaps for more than anything, because it's MS. Forget cool features like anti-phishing in IE7. Lets step back here and look at Tiger Beta 1... it crashed only a daily basis and had very limited new functionality. It was nothing like the final release. Yet here we're comparing Tiger release to Vista Beta 1.... Anyways, like Apple, I'm sure MS has quite a few tricks up their sleaves which we haven't seen in Vista B1.
The simple fact is that recruiters and HR folks look for keywords. Certification acronyms are a major part of them. While they hold no real technical merit, non-technical employees/companies don't know that.
Uhm, gmail does support HTML email...
Wanna know something? A lot of 'crackers' grow up to be 'hackers'.
I really don't understand where you're going with DCC... What does the fact the two DCC/IRC clients communicate with eachother directly have to do with anything?
Are you saying that if they aren't proxying through a 3rd party that there's no other factors to consider when identifying the source of latency?
I really don't give a shit.
The only difference is they don't have any Jedi fighting for them.
So you're saying you consider DCC as an efficient file transfer protocol?
If they're using the same protocol for file transfers, why would you assume it's the protocol that's the bottleneck?
Anyways, no one with a clue would use IM protocols for file transfers and expect high performance in the first place.