Ah, good old fashioned flamebait. I don't get to see many people make asses of themselves anymore, so I thought I'd drop in to tell you how much of an ass you're making of yourself.
Root level exploits for Windows are released nearly every week. Sometimes its Outlook, sometimes its Internet Explorer, sometimes it's IIS... the list goes on and on; it's Russian Roulette--you never know what it's going to be. That means that stupid advice like "automatic update" doesn't work--different people have different purposes for their machines. So don't expect when you use half-assed general prescriptions like "automatic update" that someone should listen.
You don't even have a clue, do you? Beyond deploying someone else's pre-packaged, pre-planned network of PCs that are all exactly the same, that all get their network information from a DHCP server (that someone else set up), you don't know shit. Yeah, if we all had to take care of the simple shit that you do, automatic update would be the answer.
*Yawn*
You obviously understand that different computers have different purposes, and therefore require different treatment. But you have one asshead idea of how to take care of computers differently.
Even worse--when someone responds to your lame excuse for understanding telling you that automatic update no-workee, don't pretend like you were giving advice for a specific instance.
I mean, that's just stupid. Microsoft's patch mechanism is broken, from its design to its implementation, it's broken in so many different ways it's just pitiful. And you have the gall to tell someone that they should be using it--no matter what their situation...
Magic 8 ball says you need to get another job soon. The days of bullshit administration are gone along with all the venture capital.
So why don't you cry some more about how we sound like old women, or cry about how we have nothing to say.
Go ahead, little one--cry.
Re:FUD through "positive assertions"
on
Unix Isn't Dead
·
· Score: 1
Marketing fuzz talks about "excitement" surrounding things. Everyone else sees the practical, nearly insurmountable hurdles ahead of Microsoft if it thinks it's going to control the rest of the computing world as easily as it stole the desktop.
The irony is that Microsoft spent years selling crap products with good marketing. The business was the icon of the "American Dream" and Bill Gates was the idol of every MBA. Now that's come full circle; many of Microsoft's products can stand on their own--but their business practices are holding back their products because the Microsoft brand name has become a stigma (i.e. XBox flops in Europe and Japan).
After Enron, doing business "the Microsoft way" has itself become a liability; as the US Senate talks about closing tax loopholes Microsoft uses so gratuitously to pay employees, and as more and more investors want dividends from their stock, you can rest assured that things will never be "business-as-usual" again for Microsoft. (A case in point: around Microsoft--for the first time ever--there's talk of hiring freezes.)
Ironically,.Net itself may be an excellent implementation and enhancement of what Java gives, but it's inherently crippled as a Microsoft product.
This echoes too much of the Nazi idea of nationalistic purity.
H1B workers don't take "American" jobs, corporate officers and business owners give "American" jobs to people who are willing to work for the wage corporate officers are willing to give. (They need to protect that 418:1 salary ratio.)
The whole discussion is much too obtuse to begin with. Generalizing and blaming H1Bs for taking jobs is just lightly veiled prejudice. Each situation is different; just like the original poster can't simply lump 'merikans into a whiny bunch of idiots, you can't simply lump and blame H1Bs for doing anything as a whole. That's bad enough in itself--but the real fallacy lies in the idea that you can blame someone just for being willing to work.
Funny, there's still people around who really think that they have some additional rights, or are implictly better than someone else simply because their mother happened to be in a certain geographical location when she went into labor.
Ah, good old fashioned flamebait. I don't get to see many people make asses of themselves anymore, so I thought I'd drop in to tell you how much of an ass you're making of yourself.
Root level exploits for Windows are released nearly every week. Sometimes its Outlook, sometimes its Internet Explorer, sometimes it's IIS... the list goes on and on; it's Russian Roulette--you never know what it's going to be. That means that stupid advice like "automatic update" doesn't work--different people have different purposes for their machines. So don't expect when you use half-assed general prescriptions like "automatic update" that someone should listen.
You don't even have a clue, do you? Beyond deploying someone else's pre-packaged, pre-planned network of PCs that are all exactly the same, that all get their network information from a DHCP server (that someone else set up), you don't know shit. Yeah, if we all had to take care of the simple shit that you do, automatic update would be the answer.
*Yawn*
You obviously understand that different computers have different purposes, and therefore require different treatment. But you have one asshead idea of how to take care of computers differently.
Even worse--when someone responds to your lame excuse for understanding telling you that automatic update no-workee, don't pretend like you were giving advice for a specific instance.
I mean, that's just stupid. Microsoft's patch mechanism is broken, from its design to its implementation, it's broken in so many different ways it's just pitiful. And you have the gall to tell someone that they should be using it--no matter what their situation...
Magic 8 ball says you need to get another job soon. The days of bullshit administration are gone along with all the venture capital.
So why don't you cry some more about how we sound like old women, or cry about how we have nothing to say.
Go ahead, little one--cry.
Marketing fuzz talks about "excitement" surrounding things. Everyone else sees the practical, nearly insurmountable hurdles ahead of Microsoft if it thinks it's going to control the rest of the computing world as easily as it stole the desktop.
.Net itself may be an excellent implementation and enhancement of what Java gives, but it's inherently crippled as a Microsoft product.
The irony is that Microsoft spent years selling crap products with good marketing. The business was the icon of the "American Dream" and Bill Gates was the idol of every MBA. Now that's come full circle; many of Microsoft's products can stand on their own--but their business practices are holding back their products because the Microsoft brand name has become a stigma (i.e. XBox flops in Europe and Japan).
After Enron, doing business "the Microsoft way" has itself become a liability; as the US Senate talks about closing tax loopholes Microsoft uses so gratuitously to pay employees, and as more and more investors want dividends from their stock, you can rest assured that things will never be "business-as-usual" again for Microsoft. (A case in point: around Microsoft--for the first time ever--there's talk of hiring freezes.)
Ironically,
H1B workers don't take "American" jobs, corporate officers and business owners give "American" jobs to people who are willing to work for the wage corporate officers are willing to give. (They need to protect that 418:1 salary ratio.)
The whole discussion is much too obtuse to begin with. Generalizing and blaming H1Bs for taking jobs is just lightly veiled prejudice. Each situation is different; just like the original poster can't simply lump 'merikans into a whiny bunch of idiots, you can't simply lump and blame H1Bs for doing anything as a whole. That's bad enough in itself--but the real fallacy lies in the idea that you can blame someone just for being willing to work.
Funny, there's still people around who really think that they have some additional rights, or are implictly better than someone else simply because their mother happened to be in a certain geographical location when she went into labor.