Microsoft up to Old Tricks Again
Anonyous Coward writes "According to ZDnet UK News, Microsoft is up to its old trick of breaking competing products by changing Windows. This time it's NT service pack 6, which strangely has a problem with Lotus Notes. It denies users 'access to Lotus Notes on NT unless they have been granted administrative access to the
entire network.' So much for the 'findings of fact' putting Microsoft under pressure to stop this sort of thing." Related news: CEGadgets.com publishes the latest NT security hole.
On the other hand, either way the end result is still the same in that Lotus gets broken, and that should have been caught in the extensive (yeah right) testing done by MS prior to releasing this beast on the world
Microsoft up to its old tricks? Has Slashdot finally sunk to such depths that it needs to create bogus headlines like these?
Please name me one operating system that has to, and in many cases succeeds in inter-operating with so many other systems. The weight that Microsoft carries and the scrutiny under which it carries that weight should be a warning to everyone who wants them out of the way.
Asinine headlines like this one from "Roblimo" only have a place with the rest of the quacks looking for "the smoking man" and UFOs. Because you are making the rest of us look like those quacks when you post that garbage here.
Here is to hoping that Atlas shrugs.
(And take note this post was written in Netscape, under Linux 2.3.x)
http://windows.scares.us
It was probably a mistake.
If it was intentional, then it sure lends credence to the speculation that there are those in MS who really want MS to be broken up. The theory goes that Bill Gates is tired of running Microsoft and would rather be a media/on-line/banking mogul. He really can't go into those markets as aggressively as he would like while there is continual anti-trust review of every move. Remember that the Intuit deal was quashed by the Feds, and that was Microsoft's gambit to enter on-line banking.
I find that theory a bit far out. How do you really run a conspiracy like that? I mean, it only takes one MS engineer who was familiar with some testing or development effort that would break Lotus to go to the press. Remember, the Halloween documents were leaked from inside MS.
Microsoft is promising a hotfix.
MSFT has been collecting the benefit of the doubt for so long (i.e., 'trusted', as in trusting the fox to guard the henhouse) that now the tide has turned and even HONEST MISTAKES are perceived as wilful and malicious anti-competitive measures.
Spread enough FUD and it'll eventually come back to haunt you!
Chuck
try { do() || do_not(); } catch (JediException err) { yoda(err); }
Is there ever going to be a separate Micro$oft section on /.? It would be nice for the some folks to get their fix in one place, and have highly applicable M$ stuff show up on the "front page".
This constant new old news gets, well, old. But when I have the time, I definitely like the laugh/throbbing veins, depending on the story.
~afniv
"Man könnte froh sein, wenn die Luft so rein wäre wie das Bier"
~afniv
"Man könnte froh sein, wenn die Luft so rein wäre wie das Bier"
Richard von Weizs
----
----
"Oh, bother," said Pooh, as he hid Piglet's mangled corpse.
I don't know if this was deliberate (I kind of doubt it), but if it's not deliberate it betrays an incredible degree of incompetance on Microsoft's part.
One of the reasons NT is so expensive is the heavy duty testing that goes into the product. Are we really to beleive that MS didn't notice that they broke a major application?
If they didn't notice, they deserve to be lynched for gross incompetance. If they did notice, they should have either 1/ fixed the service pack, or 2/ notified Lotus well before the release so Lotus could issue a patch.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
http://www.ddj.com/articles/1993/9309/9309d/9309d. htm or just click here.
Chuck
try { do() || do_not(); } catch (JediException err) { yoda(err); }
Microsoft is so focused on rushing Windows 2000 out the door, how could they have time/people to test "every" NT application on new NT4 service packs? Remember how crappy SP4 was? SP5 was OK because it was much smaller, but I'm not surprised SP6 is crappy. The press is turning up the heat as Microsoft continues to slip the Windows 2000 ship date. If you were Microsoft what would you do, focus on NT4 SPs or Windows 2000? From a financial perspective, Microsoft will make big cash money with Windows 2000, while NT4 SP development time/people/equipment is just a cash sinkhole.
Windows NT is a huge house of cards. Microsoft can't touch the code without a few cards falling. Here is a great article by Nicholas Petreley from the now defunct magazine "NC World": Will Windows NT develop into a super-OS or an unmanageable disaster?
Also, to quote Microsoft's own Jim McCarthy in Dynamics of Software Development (an insightful but "fluffy" book, BTW): "Shipping a product is like watching a large-sized serving of quivering Jell-O. Gradually, the Jell-O slows its vibrations. But then you fix a bunch of bugs, and it starts quivering again. Then slowly, ever so slowly, the quivering subsides. You wait, focused and primed, for the instant the Jell-O stops shaking. Then... you ship it! And then it starts shaking again."
cpeterso
However, my suspicion is that MS hardly cares any more whether its OS works well with anything other than MS products. Now that they have the dominant office suite, the dominant web browser, and are pushing MS alternatives to practically every other mass-market software there is, why should they care whether anybody other than MS can compete and develop stable programs for Windows?
They don't adequately test 3rd-party software compatibility, and the problem is that they can get away with it.
The ridiculously high number of API calls for Windows (and the fact that they're constantly increasing) only makes sense if they don't care about 3rd-party developers being able to keep up.
Think about it: if Windows didn't have the monopoly on desktop OS that it enjoys now, would anybody in their right mind choose to develop software for it? Would they really want to learn the 2500-or-so API calls, only to have an unknown number of them be obsolete when DirectWhatever 9.0 comes out in another month (timed to coincide with the splashy release of MSWhatever 1.0)?