It could happen... I don't think it's likely but it could happen.
If it were to happen it would cause a huge stir in the marketplace, a lot of people would lose their jobs and the first 6 months would be crucial.
To me, the people losing their jobs part just sucks, I know what it's like to be acquired then being told that X percent of the work force is gone. It's unpleasant. However, as long as all the changes were handled quickly and efficiently the stir that would be created, spun correctly, could be a huge profit maker for microsoft and, depending on the direction the company goes, could be a huge win for consumers as well.
Again, I highly doubt any of this is going to happen.
So that was useless to read. Oh well, my two cents:P .
While it's true that most of us (speaking from a software dev's and previous support analyst point of view) are stressed. We aren't overly stressed to the point of snapping when the smallest thing goes wrong. I'm used to having things go wrong, unexpected bugs popping up, code just not compiling... etc etc, as I think most developers are. It's a stressful job (particularily close to release date), but so are most. I certainly wouldn't call it "Dangerous levels of stress".
I get roughly 5-10 personal e-mails on a daily basis in my gmail inbox(not including responses). I keep every e-mail. I respond to most. It keeps a trail of what has been said and done so 2 years later when someone asks if you have that program that they sent you, you can say YES. All you have to do (in gmail at least) is perform a search.
I'm a supporter of not deleting e-mails. It gives you deniability and you never have to think "Darn, I wish I had that file that John Q. Nobody e-mailed me"
Wouldn't it be better to devote more resources to a global wireless network. While there are security flaws in both, it seems to me that have WAP's virually everywhere seems a hell of a lot easier than keeping up with the growth and changes of the internet.
Slashdot Mirror
It could happen... I don't think it's likely but it could happen. If it were to happen it would cause a huge stir in the marketplace, a lot of people would lose their jobs and the first 6 months would be crucial. To me, the people losing their jobs part just sucks, I know what it's like to be acquired then being told that X percent of the work force is gone. It's unpleasant. However, as long as all the changes were handled quickly and efficiently the stir that would be created, spun correctly, could be a huge profit maker for microsoft and, depending on the direction the company goes, could be a huge win for consumers as well. Again, I highly doubt any of this is going to happen. So that was useless to read. Oh well, my two cents :P .
While it's true that most of us (speaking from a software dev's and previous support analyst point of view) are stressed. We aren't overly stressed to the point of snapping when the smallest thing goes wrong. I'm used to having things go wrong, unexpected bugs popping up, code just not compiling... etc etc, as I think most developers are. It's a stressful job (particularily close to release date), but so are most. I certainly wouldn't call it "Dangerous levels of stress".
I get roughly 5-10 personal e-mails on a daily basis in my gmail inbox(not including responses). I keep every e-mail. I respond to most. It keeps a trail of what has been said and done so 2 years later when someone asks if you have that program that they sent you, you can say YES. All you have to do (in gmail at least) is perform a search. I'm a supporter of not deleting e-mails. It gives you deniability and you never have to think "Darn, I wish I had that file that John Q. Nobody e-mailed me"
Wouldn't it be better to devote more resources to a global wireless network. While there are security flaws in both, it seems to me that have WAP's virually everywhere seems a hell of a lot easier than keeping up with the growth and changes of the internet.