More on Longhorn 624
An anonymous reader writes "Everything I have read concering MS's future plans: Palladium, Client/Server tie in, Office 11 breaking backward compatability, 3 year licensing plans, product activation - all leave me with a foreboding sense of the potential synergy for furthering Microsoft's goals of complete domination. Now this article tells about Longhorn's new filesystem being based on the the future Yukon server. And surprise it will only work with new hardware, which they want to be Palladium enabled. And all pitched to you under the rubric of Security & Efficency.
For years MS has been accused of only wanting
people to run MS Software. Now according to the article, 'Microsoft doesn't think computer users should have to use one program to read and write a word-processing file, another to use a spreadsheet, and a third to correspond via e-mail. Rather, the company thinks, a single program should handle it all.' One program to rule them all, one program to bind them, indeed."
Re:Certainly radical... (Score:3, Insightful)
Re:Certainly radical... (Score:5, Insightful)
Corporate computing is not some ideal world... it's all about money, money, and more money. Computers exist in the first place to save time (and therefore money).
Scary quote (Score:5, Insightful)
I sure hope he isn't talking about security in general, because I sincerely doubt that Palladium will yield any kind of increased security other than security for MS's bottom line. The ignorance of that statement is astounding. Even if Palladium-esque code signing does increase security the added complexity is sure to keep the security people busy for years to come.
foreboding sense? but what if the software's GOOD? (Score:2, Insightful)
Any way I phrase this, it's going to sound like a troll; but... what if the software, once integrated, ends up being GOOD? What if it makes people more productive, and they're WILLING to pay for it? Because if they're not, there are open-source alternatives available (as you probably know, since you're reading this in a Slashdot forum).
I am already tremendously more productive developing at work under Win2000/XP using Visual Studio and Office (yes, even including the synergistic Outlook) than I ever could be with the open source equivalents. Microsoft has sunk more time and effort (read: money and person-hours) into making these programs intuitive and largely self-configuring. Sure, their programs sometimes don't work properly. And in a moment, several of you will make fun of me for saying that MS software is frequently intuitive to work with. But here's a dirty little secret: open source software contains bugs, too! And it's not even remotely as intuitive or polished. It's all about the Mom benchmark: she could never, EVER muster up the courage send me e-mail from overseas using the 'intuitive' interfaces found on a Linux box.
Forboding sense? Nonsense. I'm hoping they make something I'd WANT to pay for. If you don't agree, just keep using the open source alternatives. The sky is not falling.
Is that a new idea ? (Score:5, Insightful)
Kidding aside, the idea of hiding to the final user the application layer may be a good one. If this was done openly (i.e. documenting the API that each class of applications should have and allowing administrators to switch one application with another, from a different vendor, without troubles), could be a good step to make computers easier to use.
Knowing Microsoft, however ...
Re:Certainly radical... (Score:5, Insightful)
If any company is capable of doing this right now it is Microsoft. The idea has a certain charm, it is a logical extension of components and virtual machines.
Microsoft engineers don't seem able to program their way out of a wet paper sack, let alone implement security features.
Individual programmers at MS probably have the same skill levels as those at any software company. The ad-hoc feature growth of many MS products is likely the cause of most of the security problems (and many stability problems as well).
jack of all trades.... (Score:3, Insightful)
But seriously, isnt that what joe consumer wants? Something which IS jack of all trades but master of none
Word and excel are both more complicated than joe consumer wants - so what their trying to do is ressurect MS works and shove outlook and MSN messenger in there aswell?
That seems to me like it would really appeal to the OEMS, so thats what joe's gonna get...
Oh please! (Score:5, Insightful)
Ok, not that the conclusions are then worth anything, but still some remarkable opinions are ventilated in the article, even when you take into account the conclusion-based-on-rumour factor.
For example:
"Neither Linux nor Unix ties the operating system to hardware," he said.
Come again? We're talking about a new PCI architecture here, not about a new soundcard!. And since when can I install AIX or HP-UX on ANY i386 system? Ever installed Solaris for Intel on an Intel machine you also happen to use as a workstation (f.e. with Linux on another partition?). The 'he' person definitely doesn't have a clue whatsoever about tying an OS to hardware. It's in all situations very important the OS works flawlessly with the hardware it's installed on, so yes, every OS is tied to a subset of available hardware. Big deal.
Ok, then we move on to:
"I'd like to see Microsoft act like the operating-system leader it is, not promising scores of new features or letting rumors fly but stepping forward and saying, 'We will have X, Y and Z features and not A, B and C,' " he said. "That would be leadership, especially when so many people are dependent on you."
WTF is the 'he' person to ask for this? First he throws in the rumours no-one confirmed as being true (the article clearly states MS didn't say a word about any detail concerning Longhorn) and then he wants MS to clear the sky for him about the rumours and to step forward about any featureset they'll implement in an OS which isn't even in Alpha-stadium nor a releasedate has been set.
Like Linus is going to talk about features in the 3.2 kernel, released somewhere in Q4 2004, "because so many people are dependent on you.". Sure...
Paranoia or marketing to the corporate types (Score:5, Insightful)
The 'database' file system is not new (and many on
Keep in mind though, that this type of pitch is being made to the corporate IS types. Stories like this are 'leaked' to help test the waters. The money just isn't out there any more for the latest bleeding edge operating system and Office upgrades. In order to pry the dollars out of corporate boards these days, you have to show real value, and the IT types these days only know one way to count (with their socks on that is), and that is the magical phrase "TCO". You can guarantee that the M$ marketing types will be selling the reduced training costs of the one-application scheme.
Maybe though, before completely calling it a waste of code, we can judge the ideas on their technical merits and make fun of the marketing slime later? Of course, if your just interested in getting the story posted, keep the chicken little act up
Re:Scary quote (Score:3, Insightful)
no more MS users......=) (Score:2, Insightful)
Re:All anti-MS, all the time (Score:3, Insightful)
In market forces I trust (Score:5, Insightful)
I think some people posting on this topic have spent too much time watching the X files. It's only an operating system guys, and, if it is as radically different to previous versions of Windows as is claimed in the article, it is going to have to compete not only with Linux and friends, but also with W2k and XP.
So if it really does offer something fundamentally new and useful that outweighs the disadvantages of DRM, people might buy new hardware and switch. If not, they won't. And even if the new OS is a runaway success, it will have to talk to W2K, XP and Un*x servers or it just won't work on the current Internet.
In other words, if things pan out as stated in the article (which is by no means certain), Windows 04 is going to have to compete without most of the advantages enjoyed by previous versions, so it should be a much more even fight between MS and OSS. And could it be that this is what has really got everyone spooked?
Re:Scary quote (Score:3, Insightful)
Remember that in the end, security is as strong as the weakest link in the chain, usually the user. A common 14 year old AOL script kiddie who faithfully opens his pr0n.jpg.vb email attachments while using various "security tools" found on various "security related" sites (read: Trojans. Lots of Trojans.) can turn even an OpenBSD box into an insecurity-ridden deathtrap.
Holy crap! (Score:5, Insightful)
Scary stuff ... (Score:3, Insightful)
I'd like to see Corporate America swallow that wad
there is no strategy there (Score:5, Insightful)
If Microsoft is going to put everything into a single program, presumably with loadable .NET-based components for extensible functionality, why did they just spend a decade moving towards a UNIX-like multi-process operating system? The NT/XP kernel and technologies like XML are redundant and inefficient for building that kind of system.
What this tells me is that the company has no clue where they are going. Most of their technologies (NT/XP, C#/.NET, XML/SOAP, DRM, etc.) are "me-too" reactions to industry fads. And a few ideas are somewhat dated gee-whiz gearhead ideas that seem to pop up randomly out of their research organization ("database-as-filesystem", etc.). The only thing that is predictable is that Ballmer and Microsoft marketing will try to figure out how to sell that stuff to the public.
Re:Especially when you see the adds :) (Score:3, Insightful)
Then again perhaps its because the (maybe) 5% of the world that use Linux come here to this one place and they want to try and convert them back. Of course, Dell and AOL advertising in hardcore magazines like PCXL found out the hard way that this approach doesn't work.
Yukon Good Idea (Score:5, Insightful)
I'll use Oracle as an example because I'm more familiar with it. When you store things like PowerPoints and the like into Oracle, through their products like InterMedia you can automatically do things like search for content insides of these "opaque" files (not just look for file names in a filesystem directory), automate metadata generation (e.g., width/heigh/color depth, etc for images), transcode from one format to another, etc. At this point, most of the capabilities I've seen are "toolkit" oriented. That is, they enable developers to build apps that take advantage of them but aren't necessarily suitable for use directly by end users. I believe all of oracle.com is managed in this way, so check it out.
If Yukon is basically doing a similar thing in extending SQL Server to support unstructured content well, this could very much be a good thing in terms of functionality.
Also, don't be so quick to dismiss MS's security talk as just another way to take over the world. Obviously, these guys are very focused on market success and very focused on competition with GNU/Linux and free software. But they understand that in general security flaws have been a huge achilles heel for their products and they are doing a number of things top to bottom throughout their development process to really wring out security bugs and make more robust software. I can't reveal what most of this is due to non-disclosure, but from what I've seen MS are treating security very seriously and are focusing on the "security gap" in the same way they've focused on competitor functionality in the past.
You're concerned *now*? (Score:5, Insightful)
Will due respect (perhaps) to the analysts, the article reads more like a cute marketing ploy or extreme FUD: haven't Microsoft brought out enough drivel in those areas to warrant even more coming from unofficial/non-connected sources?
I mean, please, when people are quoted as saying "Neither Linux nor Unix ties the operating system to hardware,...This could bring [for Windows] a higher level of security than anything we've ever seen. It will almost completely prevent the platform from being compromised." then exactly how much respect does the article warrant? Not only are the quotes lacking in true factual content, but the majority is damn right humourous (in the groaning sense)!
[Disclaimer: I'm ranting at the article and its content, not the fact that it was submitted to
Re:Bearer of bad news (Score:2, Insightful)
Re:In market forces I trust (Score:5, Insightful)
What if :
You are not taking the long view (Score:5, Insightful)
1. Stop fixing win95 problems when they pop up (yes they do pop up, as certain as the sun rising every day). Eventually retire the OS so that users of this ancient operating system become software renegades, but first make it even more difficult to use than it was when it first came out so that there won't be much fuss when it's eventually retired.
2. Use those billions in the bank to pay a few companies to make software that requires features in newer versions of windows, i.e., not backwards-compatible with win98/ME any more. Microsoft has the money to play this waiting game, and they face no threat from the courts, so every day their influence grows. X-Files indeed- I think you're the one living in the imaginary world.
You say it's just an operating system, why have I been *forced* to use it at every job I've had since at least 1997? They are a *monopoly* and they abuse their power in ways that make life miserable for the rest of us.
Re:Scary quote (Score:5, Insightful)
Perhaps it will help to fill in the hidden blanks in the sentence:
"This could bring a higher level of security than anything we've ever seen. It will almost completely prevent the platform from being compromised. [By the owner. MS, content providers and 12 year olds from countries you've never heard of will be free to walk all over it as usual]"
There, that makes a lot more sense.
Opportunity for Open Source (Score:5, Insightful)
Obviously, Longhorn is not going to come out as early as 2004-- the PI article is at least fair enough to quote another source who knows better than to believe the MS PR. Since the new OS is not likely to be out for another three years, this is a chance for the open source community to make its case to the public of why it should try its products.
The first case for open source will be, "You don't have to give up your old computer!" We already know that Linux and other OSs can be installed on x86 hardware; it has to be easy to install, and it has to have all the other things that people are accustomed to having on their machines. Finally, it has to have programs that are compatible with common file formats, like MS Office. With OpenOffice, that last need has largely been fulfilled, where it comes to productivity.
What would also be helpful is to pitch open source products to hardware manufacturers, as a way to sell more units. If not to the consumer market, then to the business market. Having Linux pre-installed on machines would make the transition to open source a lot easier for the enterprise. Of course, with Longhorn, the promise for the HW people is that they can sell a lot more units in the future with Longhorn. But, in the meantime, they may be struggling with machines that can only be loaded with warmed over versions of XP.
The other thing that has to happen is that people need to be made aware of what DRM really represents. If you don't like MS having admin rights on your machine (as they do with the latest SPs on Win 2k and XP), you sure as hell won't like DRM-enabling Palladium. It's about freedom, and I think a simple slogan on a T-shirt to get this home could be: "DRM=Total Information Awareness". "Trusted Computing" is just a slogan, when the count on security patches for Windows and related products this year is 65; for open source, it's closer to 10. Which do you think is more "trustworthy"?
Re:How exactly would Linux handle 5000 developers? (Score:3, Insightful)
The magic pixie dust is the free flow of information. Linux development need not concern itself with keeping the source code a deep dark secret, anyone who wants to can just grab the entire source tree and study and reuse any part of it that they choose. There's little need to 'manage' a team that is developing a subsystem. No charts and graphs and timelines to slavishly adhere to. No danger that you'll come in in the morning and discover that your latest revision (the one with the bug) was declared 'released' and burned to CD.
All of that stuff happens when source code must be a protected secret, and it adds a great deal of management overhead.
Comment removed (Score:5, Insightful)
Re:Certainly radical... (Score:4, Insightful)
chrisseaton wrote:
The research project was Millennium [microsoft.com] , from the late 1990's. What, you think Microsoft came up with "trustworthy computing" when they did that memo? Or that they started on Longhorn the day XP was released? They have been working on this scheme for a looong time. They had to build .Net just to have a distributed platform-independent development tool they controlled. They are literally betting the company on this.
Yes, but unfortunately it is Microsoft. That means bugs, like the flaw [cdi.org] in SQL Server (on which Yukon is based) that may well have eaten some of our nuclear materials.
Even if Microsoft made it bug free for once, they are the last people on the planet I'd put in charge of a world-wide distributed network. I don't know who would be safe to have administrate the thing.
To Microsoft:
The crown is not yours.
Footsteps drum a dirge of doom
By nuclear rage!
The world's great hero,
Dreaded God and Monster King,
Millennium ends.
Re:Scary quote (Score:5, Insightful)
A secure OS in that context is impossible to write; control over the hardware equals control of the contents on the computer, so they shouldnt really be criticised for being unable to implement that without hardware support. It will never be entirely successful but they can push the barrier for copying to such levels that you need to be able to buy your own CPU manufacturing run to be able to backup any data you want on your computer.
A secure OS in the context of preventing access for intruders is far more possible of course. That they cant do that has been obvious for decades.
Re:foreboding sense? but what if the software's GO (Score:3, Insightful)
Also, your logic is flawed between OSS projects and proprietary efforts like windows. Certainly ten years ago there might have been a problem with no funding and crappy UIs, but if you take your head out of the sand and look around, you'll realize that there are plenty of OpenOffice.orgs, TransGaming WineXs and Lindowses. Your arugement falls apart the second companies start backing (or creating) Open Source projects.
Re:And there will be one Master Ring (Score:5, Insightful)
The number one reason that _users_ are using windows is that when you go to the shops to buy a PC you don't get much choice and if you even asked about the software the sales people would become very confused and wonder what you were on about.
The PC was never supposed to be a home computer OR an office computer. It shows this and so does windows.
One Program? It has been done, even by Microsoft. (Score:1, Insightful)
Horrible thing? Sounds like something KOffice already does.
Re:You are not taking the long view (Score:5, Insightful)
Stop fixing win95 problems
It's a seven year-old product: why should they keep fixing it? If I post a bug in a seven year-old version of emacs to a newsgroup, I'm going to get flamed, and rightly so. In the case we are discussing, people could stop at XP, and MS's longstanding policy is to support the previous OS, so I wouldn't even start to worry until 2006-2008
Not backwards compatible
Is all the open source stuff released this year compatible with the original Linux kernel? Or even with the pre-version 2.4 kernel? Should it be? Would this make any sense whatsoever? I think MS's main problem is that they spent far too long trying to be too backwards compatible. Most OSS projects don't have this problem because they don't have a non-geek user base...
Forced to use Windows in every job
Nonsense, you just picked the wrong jobs. It's either a life and death issue or it isn't. If it is a life and death issue, make not using Windows the first criterion for choosing an employer and live with the consequences. If it isn't, take the money and stop complaining. I've never used Windows in any job at any point, which might be why I probably earn less than you do. I'm about to install W2K on one server, but that was my choice, no-one made me, and the reasons for doing so have more to do with the lamentable state of much OSS applications software than with Microsoft's monopoly.
Re:Its been done (Score:2, Insightful)
No system is secure: Social Engineering. Education (Score:5, Insightful)
By Social Engineering I refer to the oldest form of hacking: convince someone to do something for you on his/her machine. No hardware, software, or operating system can protect a user from this today.
By user's naiveness I mean that most users (who naturally are not tech-savy) simply open every email attachment they get, or simply click on "yes" or "ok" on every pop up they see without first reading. Combine this with Social Engineering and I really don't see how Microsoft will stop the wave of attacks against windows machines.
The only thing I have seen so far that works to a good degree is Java's sandbox model, where in a sense every program is an island unto itself, and if it wants to communicate with other programs it needs explicit permissions or use well-document open-standards-based protocols. However even this suffers from user's naiveness sindrome.
Bottom line: Security is an EDUCATIONAL issue. Create awareness and teach people the basics of security (don't give your credit card number to ANYONE who calls you, don't open attachments from people you don't know, use an updated virus scanner, patch the latest discovered holes in your OS, use a firewall, etc), if we manage to do this (a daunting task), I think we can get MUCH farther in the security arena than instead taking all our freedom away in a completelly-controlled and restrictive environment.
Re:Scary quote (Score:5, Insightful)
yeah, it really is a rumor-mongering article. What disturbed me most about that quote was the attitude of the analyst, not so much MS' plans. I doubt that MS really thinks that Palladium will solve all their security problems; but that's how they are planning to sell it to the managment types. They've simply decided that thanks to all the "terrorism" uproar coupled with increasing criticism of their own track record, that security is an excellent marketing point to use these days. They are going to use talk of threats to enact hardware enforced DRM while at the same time selling this as a "security" feature to those who don't know better.
What I was criticizing was the wholesale manner in which the analyst appears to have bought into that marketing strategy. I'm disturbed that someone who could be my boss may be reading reports like that and believing them.
Re:Hmmmmmm (Score:5, Insightful)
My observation over time has been that Linux seems to stay about 3 or 4 years behind Windows in the area of user interaction. For example, the latest RedHat 8.0 release with KDE finally has an elusive "buttery smoothness" that I first noticed with Win2K. (Yes, I know Macs probably had it since 1932, but I don't use those.) RH8 even supports mostly point-and-click administration functionality.
The thing is, going forward from here, I don't see the incremental improvements in OSes as being very compelling. For example, I've had no reason whatsoever to use Windows XP over Win2K. This means that even if the Linux user interface remains a few years behind Windows, the difference becomes less and less important over time.
As far as a database filesystem, I think it will be like the NT security model vs UNIX. Better in theory, but too complicated for anybody to actually use effectively. In the past, the NT security permissions were usually left too loose because nobody wanted to deal with figuring out appropriate settings. Likewise, I'll bet that in the real world, the relational database filesystem will be mostly organized into a strict heirarchy just like today. The bottom line is that it won't have much value for the average user.
Re:Been there, done that. (Score:5, Insightful)
Which one? RMS didn't write the first emacs, that was Gosling.
The slashblather today is pretty much of the form 'Microsoft is doing nothing new because it never does', followed by 'Microsoft is going to change the hardware'.
Microsoft does not have a reputation for security, but they do employ some of the top people in the business. Assuming that all those people become imbeciles the minute they move to Redmond is just a self serving slashdot dellusion.
Not so long ago the standard repost to any Microsoft post was the time a system stayed up before the blue screen of death. Funny thing, you don't hear that half so often since Windows 2000 and XP hit the stores.
Not so long ago UNIX had a lousy reputation for security. That took about five years to change as people started to deploy Kerberos and ssh to patch up some of the more eggregious holes.
Basically there are two routes the open source community can take. Route one you sit arround and congratulate each other while Microsoft goes out and eats your lunch, or you could start to look at ways to extend the security model of Linux to be competative. The execs at Apple, Wordperfect and Lotus took the first approach so you would be in good company.
It's called "remedy" for monopolization (Score:3, Insightful)
To understand the difference, see my article "Anti-globalization vs. anti-capitalism." [underreported.com]
Reminds me of OpenDoc (Score:2, Insightful)
Very surprised at this article (Score:2, Insightful)
(1) No "Subscription" model
Wasn't it MS who pushed the failed ASP (application service provider) concept so many dot-bombs followed? With even game makers like Electronic Arts drooling of $10 monthly service fees for the Sims Online, I can't believe there is no mention of what MS is up to
(2) Forget TCO, how about ROI
When I used to put in my two-cents on new product development and build vs. buy decisions, TCO was only an ingredient in the formula all were interested in, Return On Investment. I see fewer and fewer compelling reasons to move to the latest for MS - so many small businesses run on Win98 or some other 'ancient' flavor of windows becuase the HW/SW is paid for and gets the job done. Convince someone running point of sale for their small business that they should upgrade. Now flip the coin and convince a mega corp that they should spend millions on new software, TRAINING, and now, new hardware. Do the math...at a generous $2,500 per seat for HW/SW/Training, a company must spend $1 Million for every 400 employees. And those companies will want more than a wink from Bill for their money.
(3) Way to embrace the market
The presense of 3rd party apps is a mega plus for MS. By integrating all aspects of desktop publishing - presentation, documents, web sites, flow charts, e-mail, etc - there is no room to pick and choose what works best for you - there is ONLY the MS way.
(4) What MS could do
MS's only viable option, to me, is to focus on server technology and make very rich servers with high license fees for connections that will have to exist. Make the client so thin it doesn't matter what they use - old hardware, old OS, etc - because they are making recurring revenue off the license to connection to the server which is where they could add value and fight with ROI.
All your apps are belong to us
MS will screw it up (Score:2, Insightful)
Think about what this would mean. We would not have to find and open a new application for each task. We would not have to figure out what is the best format to use when we copy 'foreign' content into our word processing document. This operating system would just let us do work without the distraction of a myriad of applications and formats. This hasn't been done because it requires a level of computing power that is yet not cheap enough and programming abstraction that is not yet common. I don't know how this would be done, but the The Humane Interface [sourceforge.net] describes one possibility.
So, why does history tell us MS will screw us over with this new interface. First, the top level interface must be open and expandable. One would expect the UI to contain a set of user definable hooks that will allow the user to add or substitute filters for each type of content, and define new hooks for new types of content(think about the web browser). MS is notorious for keeping hooks secret, and secret hooks means that you are stuck with MS approved filters, which further the monopoly.
Second, the file format must be open and expandable. For people to write new filters, and create new types of content, programmer must know the storage formats and protocols. Again, MS does not create open formats, and makes arbitrary changes to formats to break compatibility with any foolish enough to reverse engineer the formats.
Third, the UI must be secure. At the base level this means that the UI must sandbox each process to insure that user processes are secure. MS is not good at the sandbox. On the configuration level, the user should have some confidence that filters will not mysteriously change. If filters can be remotely changed, then a trojan can easily be placed in a filter. MS will probably break security here because it likes the ability to configure a user's machine to MS standards. Finally, the UI must not allow all processes full functionality. For instance, foreign content should not be allowed to automatically compile as run as root. However, we see in outlook that, by default, images are loaded and scripts are executed. This gives us little hope that MS could create a secure UI.
Re:.. and in the darkness bind them (Score:3, Insightful)
Microsoft: The new version of windows will be faster, more stable, and more fun!
Tobacco: Cigarettes are stylish, fun, and we don't know anything about them causing cancer, honest!
Re:foreboding sense? but what if the software's GO (Score:2, Insightful)
Re:You are not taking the long view (Score:3, Insightful)
Because Windows is not modular and not open source. You cannot upgrade individual components. You cannot fix a problem yourself. You must PAY for bugfixes (new versions of Windows), which means you'll probably have to buy new hardware too.
"If I post a bug in a seven year-old version of emacs to a newsgroup, I'm going to get flamed, and rightly so."
Upgrading from Emacs 1 to Emacs 21 doesn't require you to pay for anything (ok, except bandwidth costs) or upgrade your hardware. Upgrading from Win95 to XP does.
You're comparing an application upgrade to an operating system upgrade.
What about Linux kernel 2.0? Still being maintained. Or even 0.0.3! Still being maintained.
"Is all the open source stuff released this year compatible with the original Linux kernel? Or even with the pre-version 2.4 kernel?"
The original (0.0.3)? Not likely. Pre-2.4? Definitely! If you recompile OpenOffice/Mozilla/Gnome2/KDE3/whatever under RedHat 6.2 (with a 2.2 kernel), everything will work just fine.
"Should it be? Would this make any sense whatsoever?"
The software work under 2.2, so I guess it does make sense.
Re:Is that a new idea ? (Score:4, Insightful)
I will give Microsoft credit for trying something new, they haven't done much of it to this point, and god knows, computers suck, they need all the help they can get.
Re:Moron (Score:3, Insightful)
But just think how simple the security bulletins would be with only _one_ Microsoft product! Gargantuan as it might be.
If you read between the lines a bit, it sounds like they want everything integrated into the operating system. That would be "one program". Good thing their antitrust trial is over.
Talk about "consumer choice". I think their ass needs to talk to their head more often. What about competing products? Irrelevant... they want to assimilate us.
Microsoft's future initiative is sure to bring about unprecedented resistence and vocalization of alternative computing platforms.
MS employee skills versus MS quality (Score:2, Insightful)
The key advantage open source has over Microsoft is not the talent of the developers (as you've said, Microsoft developers are very talented), it's the structure of most open source projects. In open source, the individual always has a say (you can patch and fix your own kernel) and even in groups, the typical individual has to pass through no more than two levels of beaurocracy (e.g. the maintainer, then Linus to get into the Linux kernel OR through your distributor's maintainer if you want to get into a distribution)
As a consequence, things like "looking good to the press" or "forcing people to upgrade" or "hiding flaws" just don't figure into the organization of open source because with open source we all make individual decisions.
It's Like That Old Saying: (Score:3, Insightful)
Blue Screens (Score:3, Insightful)
My computer blue screens more often under XP than it ever did under 98. I run a network of 2000 machines, and let me tell you, our old friend BSOD still visits on a regular basis.
I run Linux and Windows side by side on identicle hardware in production environments. Linux is just too damn simple to kill. Windows is only getting more complicated. Bugs and hangs are proportional to code complexity. Do the math.
This is correct (Score:3, Insightful)
Yes, there are more healthcare costs, but the lifespan expectancy drastically shortens, so smokers are less likely to recieve the benefits of Social Security. Furthermore, when the taxes that smokers pay that go to everyone are factored in, the researchers concluded that smokers actually are an economic benefit to non-smokers (of course, they certainly could have missed some factors).
The total economic benefit of someone smoking a pack of cigarettes to the non-smoking community was estimated to be something like ten cents, IIRC.
The overwhelming factor is that smokers tend to die early, and never enjoy their retirement.
If anyone's still dumb enough to be smoking, that study should have put them off...
Re:Is that a new idea ? (Score:2, Insightful)
Just to play Devil's Advocate here... (Score:3, Insightful)
Heh, I like Konqui. It's what IE should have been. And unlike IE it seems to get faster and sleeker and more standards-compliant with each iteration.
sorry, but you are wrong (Score:3, Insightful)
UNIX has been hardened in more than 20 years of multi-user use in some of the most hostile environments on the planet (college campuses). The entire UNIX software architecture is built for the kinds of systems on which you have hundreds of simultaneous users, dozens of which may try to break in at any time. And it stands up to that kind of assault.
Windows NT machines, in contrast, hardly ever have more than one person logged on at the same time. Almost all multiuser installations of NT are only concerned with the security of the file server, and security and privacy is really only guaranteed for files that live on the file server. Even if there were local breaches of security on the machines users log into, it's unlikely anybody would ever notice them. Furthermore, many of the NT services and user-mode libraries haven't even been designed with single-machine multi-user operations in mind. The closest to multi-user NT is Terminal Server, but that has found it necessary to put a whole other layer of insulation between different users.
So, altogether, you are wrong: you haven't been able to do that with any Windows NT based OS, ever. And chances are, you never will be. Windows NT isn't built for that kind of security, and it isn't used in that kind of environment.