Now, this may sound on the surface like an M$ slam, however that is not my intention here (as much as I dislike that company).
M$ has shown, in the past, that it is very unresponsive at times to reported security vulnerabilities. Sure, the proper thing to do would be to send the vulnerability details to M$ and have them fix it. The problem is that M$ sometimes sweeps such stuff under the rug: "Oh, no one else knows, so we can put this one off." By posting the code, it is quite possible that M$ will be forced to deal with the issue now. I don't agree with the method taken here, but considering M$'s track recond on this, this may be the only way to get it taken care of quickly.
I'd be happy enough if I could just spray it on my kids, then I wouldn't have to give them a bath! Of course, if they couldn't get dirty, I suppose they'd be pretty upset with me! LOL!
Actually, what I personally find more frustrating is that when you actually do find what you want, the download fails because either the host drops offline or refuses to accept the connection. Another little irritant is the large number of files out there that are deliberately misnamed so that when you download and open them, you find yourself dropped into someone's personal porn site, regardless of what you're looking for. I used to look for cool stuff like the blooper videos and whatnot, but I got one to many that was deceptively named. Not worth the effort, really...I uninstalled the damn thing and quit trying.
Not too long after I got into a position with an employer, part of my teammates were let go, some of them with more experience than me. The biggest problem was that the people on my specific project that were let go were more knowledgable than the rest of us.
The effects on the rest of us were dramatic, and not all of the effects were bad. We all had to rise to the challenge and figure out what the hell we had to do to make this thing go, without the benefit of the in house expertise (BTW, we were enhancing a product we authored in house). There were many, many nights where we were here late into the night, more than once past 2:00am just to figure out what was going on.
In the end, we pulled it off and emerged successful on the project, and we were regarded almost as heroes in house. We are regarded as can-do people that can rise to a challenge, but the cost to get there was enormous. We all were worse for the wear.
I have seen a trend when it comes to layoffs that is echoed in the experience I had -- for some oddball reason, it seems the management likes to trim the knowledge base at the wrong points. It stands to reason that, when letting go a very knowledgeable person, someone else must be trained up to fill the shoes of that person. This, in turn costs more money. Which is better, spending the money on a more expensive employee, and make the deadlines on time, or spend about as much to miss the deadline and train up someone new?
Yes, yes, some deadwooding goes on too, but I have seen all to often the productive ones with a higher salary cut loose solely on the basis of immediate salary concerns. I would be interested to know if others have observed the same, or if it's just been a matter of where I have been at the time...
So, the goal is thus to eliminate competiton so that those charging for the same information can charge even more for it? This sounds like a Microsoft tactic...
...but if you have to involve your PC in the process, why bother surfing from the phone at all? You get a much better viewable area, and better browse control, through a PC than through a phone's browser. Did I just misread this writeup?
I imagine M$ will never give away Winblows, as I am sure they believe that they are invincible. Why give stuff away when they can ignore the court orders and still get away with it? That strategy has worked in the past, so why is this time any different? And if Palladium makes it through...Ugh.
With Caldera and SuSE each having a stake in UnitedLinux, which one actually does the "steering" (for lack of a better expression)? It seems that even when companies cooperate, someone ultimately emerges at the leader.
I get this feeling that, like a lot of other cooperative efforts, there will be a split between the involved parties down the line (different business models, philosophies, goals, etc) and there will be separate paths taken by the different companies, and the end result will be that no one has really gained too much in the way of progress. Am I alone in this line of thinking?
Can you use firewall software to lock down any crap they install on there? With the firewall I have installed, any time any application tries to hit the 'net I get a notification and an opportunity to shut the bastard down. Perhaps it's not an ideal setup, but at least I know who's trying to talk to the 'net behind the scenes. If they *have* to install their junk on your system, this is possibly one way to maintain your privacy a bit...
Once upon a time, Symantec had a C++ compiler, and with version 7.5 (1996), the build process could be spread all over a network. This did speed up compilation times as machines that were running the build service that were more or less idle would be sent files to compile, passing back the objects and binaries as oppropriate.
Oh, by the way, that compiler is now called Digital Mars C++.
That said, all the machines on the network had to be running Windows (and at that time, I think only Windows 95 or NT were the only choices available for that compiler). Further, all had to have the same version of the compiler.
For those of us that are running Linux boxes on a primarily Windows network, this system, whether GCC or something else, would be rather hard to implement without a cross-compiler. Additionally, even if all were Linux workstations (or BSD, or Solaris, etc etc etc) wouldn't binary compatibility be driven by not just the version of the compiler but the target OS as well?
It's a noble undertaking. I hope that the developers are putting thought into all the little things like this that will make it tough to pull off.
Involving the state attorney general is an excellent idea, although I suppose that would fall into the "contact local and federal authorities" bin. I used this route several years ago to get my money back from a guy in Texas that took me for $600. I ended up getting ALL of the money back, and he ended up getting really uncomfortable scrutiny.
Now, if you pay via PayPal, that can be another issue althogether. If a seller states that he/she *only* accepts PayPal, and nothing else, there's no guarantee that the shipping address is correct. I think I would avoid such sellers.
Actually, every OTHER source I have ever seen has agreed that the death of the Amiga was Commodore's poor marketing. (IBM had the same abysmal failure with OS/2). I can't speak on the Newton, because I don't know enough about them to make a coherent statement. But, I don't think TiVo is having marketing issues like Amiga did.
One would hope that, in this sue-happy society, the Russians have considered the ramifications of a situation where something bad happens. Sure, sure, it's unlikely. But there have been enough situations where space launches have gone awry to make one think about it. (Challenger was one, but then again, that was NASA, not the Russian space program).
Maybe the winner gets to sign one of those lovely "release of liability" forms?
Just a thought.
I would imagine that a good number of those that hang out at this website remember the infamous "Halloween" memo that was an internal M$ document (it came to light during the big Nestcape/M$ trial back around 1998) that described what to do to keep Linux from rising like a fiery phoenix. The gist of it was, if my source was accurate, to change the standards every few months and force the hardware people to keep up. That way, Linux would constantly be trailing Windows on current hardware support.
Of course, M$ said it was only an engineering whitepaper that was designed to be "information only" and no plans to implement said ideas were in the works. Umm...Yeah...Right. You say it, I'll believe it, Mr. Ballmer...
This article describes a situation that eerily looks and smells like the Halloween document. Not good.
Slashdot Mirror
Now, this may sound on the surface like an M$ slam, however that is not my intention here (as much as I dislike that company).
M$ has shown, in the past, that it is very unresponsive at times to reported security vulnerabilities. Sure, the proper thing to do would be to send the vulnerability details to M$ and have them fix it. The problem is that M$ sometimes sweeps such stuff under the rug: "Oh, no one else knows, so we can put this one off." By posting the code, it is quite possible that M$ will be forced to deal with the issue now. I don't agree with the method taken here, but considering M$'s track recond on this, this may be the only way to get it taken care of quickly.
I'd be happy enough if I could just spray it on my kids, then I wouldn't have to give them a bath! Of course, if they couldn't get dirty, I suppose they'd be pretty upset with me! LOL!
[snip]
Actually, what I personally find more frustrating is that when you actually do find what you want, the download fails because either the host drops offline or refuses to accept the connection. Another little irritant is the large number of files out there that are deliberately misnamed so that when you download and open them, you find yourself dropped into someone's personal porn site, regardless of what you're looking for. I used to look for cool stuff like the blooper videos and whatnot, but I got one to many that was deceptively named. Not worth the effort, really...I uninstalled the damn thing and quit trying.
Now all I need it the airfare to get there, and I'm all set! Oh...I almost forgot...better get permission from the wife...
Damn. She said no. :-(
Not too long after I got into a position with an employer, part of my teammates were let go, some of them with more experience than me. The biggest problem was that the people on my specific project that were let go were more knowledgable than the rest of us.
The effects on the rest of us were dramatic, and not all of the effects were bad. We all had to rise to the challenge and figure out what the hell we had to do to make this thing go, without the benefit of the in house expertise (BTW, we were enhancing a product we authored in house). There were many, many nights where we were here late into the night, more than once past 2:00am just to figure out what was going on.
In the end, we pulled it off and emerged successful on the project, and we were regarded almost as heroes in house. We are regarded as can-do people that can rise to a challenge, but the cost to get there was enormous. We all were worse for the wear.
I have seen a trend when it comes to layoffs that is echoed in the experience I had -- for some oddball reason, it seems the management likes to trim the knowledge base at the wrong points. It stands to reason that, when letting go a very knowledgeable person, someone else must be trained up to fill the shoes of that person. This, in turn costs more money. Which is better, spending the money on a more expensive employee, and make the deadlines on time, or spend about as much to miss the deadline and train up someone new?
Yes, yes, some deadwooding goes on too, but I have seen all to often the productive ones with a higher salary cut loose solely on the basis of immediate salary concerns. I would be interested to know if others have observed the same, or if it's just been a matter of where I have been at the time...
So, the goal is thus to eliminate competiton so that those charging for the same information can charge even more for it? This sounds like a Microsoft tactic...
...before this can be added as a plug-in to Grand Theft Auto III?
...but if you have to involve your PC in the process, why bother surfing from the phone at all? You get a much better viewable area, and better browse control, through a PC than through a phone's browser. Did I just misread this writeup?
I imagine M$ will never give away Winblows, as I am sure they believe that they are invincible. Why give stuff away when they can ignore the court orders and still get away with it? That strategy has worked in the past, so why is this time any different? And if Palladium makes it through...Ugh.
If it was financed by the French government, does this mean that Mandrake is going to become the Renault of the Linux world? Eww...
With Caldera and SuSE each having a stake in UnitedLinux, which one actually does the "steering" (for lack of a better expression)? It seems that even when companies cooperate, someone ultimately emerges at the leader.
I get this feeling that, like a lot of other cooperative efforts, there will be a split between the involved parties down the line (different business models, philosophies, goals, etc) and there will be separate paths taken by the different companies, and the end result will be that no one has really gained too much in the way of progress. Am I alone in this line of thinking?
WMA is the highly proprietary audio codec M$ is pushing...
How long before M$ decides to file a suit against the developers of such to get their code locked down and buried? Bets, anyone?
Can you use firewall software to lock down any crap they install on there? With the firewall I have installed, any time any application tries to hit the 'net I get a notification and an opportunity to shut the bastard down. Perhaps it's not an ideal setup, but at least I know who's trying to talk to the 'net behind the scenes. If they *have* to install their junk on your system, this is possibly one way to maintain your privacy a bit...
they're so reliable and cheap, you won't need a warranty anyway
Please! What do you think it is, a Hyundai?
Once upon a time, Symantec had a C++ compiler, and with version 7.5 (1996), the build process could be spread all over a network. This did speed up compilation times as machines that were running the build service that were more or less idle would be sent files to compile, passing back the objects and binaries as oppropriate.
Oh, by the way, that compiler is now called Digital Mars C++.
That said, all the machines on the network had to be running Windows (and at that time, I think only Windows 95 or NT were the only choices available for that compiler). Further, all had to have the same version of the compiler.
For those of us that are running Linux boxes on a primarily Windows network, this system, whether GCC or something else, would be rather hard to implement without a cross-compiler. Additionally, even if all were Linux workstations (or BSD, or Solaris, etc etc etc) wouldn't binary compatibility be driven by not just the version of the compiler but the target OS as well?
It's a noble undertaking. I hope that the developers are putting thought into all the little things like this that will make it tough to pull off.
4) BEOS Makes a stunning comeback!
Naw, man... More likely OS/2, after IBM pulls its head out of its butt and figures out how to market stuff...Involving the state attorney general is an excellent idea, although I suppose that would fall into the "contact local and federal authorities" bin. I used this route several years ago to get my money back from a guy in Texas that took me for $600. I ended up getting ALL of the money back, and he ended up getting really uncomfortable scrutiny.
Now, if you pay via PayPal, that can be another issue althogether. If a seller states that he/she *only* accepts PayPal, and nothing else, there's no guarantee that the shipping address is correct. I think I would avoid such sellers.
Actually, every OTHER source I have ever seen has agreed that the death of the Amiga was Commodore's poor marketing. (IBM had the same abysmal failure with OS/2). I can't speak on the Newton, because I don't know enough about them to make a coherent statement. But, I don't think TiVo is having marketing issues like Amiga did.
One would hope that, in this sue-happy society, the Russians have considered the ramifications of a situation where something bad happens. Sure, sure, it's unlikely. But there have been enough situations where space launches have gone awry to make one think about it. (Challenger was one, but then again, that was NASA, not the Russian space program). Maybe the winner gets to sign one of those lovely "release of liability" forms? Just a thought.
I would imagine that a good number of those that hang out at this website remember the infamous "Halloween" memo that was an internal M$ document (it came to light during the big Nestcape/M$ trial back around 1998) that described what to do to keep Linux from rising like a fiery phoenix. The gist of it was, if my source was accurate, to change the standards every few months and force the hardware people to keep up. That way, Linux would constantly be trailing Windows on current hardware support. Of course, M$ said it was only an engineering whitepaper that was designed to be "information only" and no plans to implement said ideas were in the works. Umm...Yeah...Right. You say it, I'll believe it, Mr. Ballmer... This article describes a situation that eerily looks and smells like the Halloween document. Not good.