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."
.. and in the darkness bind them (Score:4, Funny)
Re:.. and in the darkness bind them (Score:5, Funny)
Three Rings for the Microsoft-Developers under the sky,
Seven for the Dwarf-VPs in their halls of stone,
Nine for IIS System Administrators doomed to die,
One for Steve Ballmer on his dark throne
In the land of Richmond where shadows lie.
One Application to rule them all, One Palladium to authenticate them,
On Application to bring them all and in the darkness bind them
In the Land of Richmond where Shadows lie.
Re:.. and in the darkness bind them (Score:5, Informative)
Re:.. and in the darkness bind them (Score:5, Funny)
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:.. and in the darkness bind them (Score:3, Interesting)
Actually, the healthcare costs are minor compared to the taxation on cigarettes. Smokers have already paid for their healthcare many times over with the additional tax on cigarettes.
Add to that the fact that most smokers will never need long term geriatric care because they'll die young, and the net health care costs for smokers actually end up being lower.
Not that this is a good thing, mind you...
Simon
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:.. and in the darkness bind them (Score:3, Informative)
If you had a sister addicted to crack, you might claim that it was "her choice," but you certainly wouldn't think that her drug dealer was innocent either.
Incidentally, you can access Exchange mail with standard unix MUA's and fetchmail.
Its been done (Score:5, Funny)
Re:Its been done (Score:5, Funny)
Re:Its been done (Score:5, Funny)
Re: (Score:3, Interesting)
u need a clue. (Score:5, Informative)
Just take a little look at security focus archives, you'll see that most of the security flaws in windows come from the tight integration of web-related scripting technologies with the core of the operating system.
Read my journal. Look at Code Red and Nimda. How do you think they spread so FAST? The best-known component of those viruses is the one triggered in an email attachment. But it doesn't stop there. The virus modifies every single html document that lives in IIS's web root, including HTTP 404, 403 *and* 500 documents, by appending a javascript window.open call to a "readme.eml" document which exploits Internet Explorer flaw with handling mime types and gets it to execute some code to further infect the machine of a user who browses an infected site.
Did you read the latest security holes? The one that leverages the help dialog box "functionality". Pretty evil.
All those components are tightly integrated within microsoft's flagship operating system, and ZERO thought was put into easily enabling or disabling those features to temporarily protect users while not impairing core functionality.
As far as i'm concerned, you've gotta be a fucking suicidal retard to be using the windows operating system for anything but playing games. Granted it does, at times, serve its purpose of a mildly friendly/convenient operating system on cheap hardware, but those security holes are just too fucking evil, and you sure as fuck get what you pay for.
Oh yeah and now Palladium. So not only are we looking at an OS featuring piss-poor security, we're also looking at a totalitarian privacy-invading roadmap. i weep for computing.
heh.
fuck windows. fuck it right in the ass.
Go Apple. [apple.com]
A new hope? (Score:3, Interesting)
Re:A new hope? (Score:3)
While you may want to discount Linux, it has a lot more support and momentum than any sort of reimplementation of BeOS. Whatever sort of technological advantage you see in BeOS isn't really the point at this time, for the short term, we need something to rally around while getting the long-term message out: "The operating system doesn't matter as long as the concern is to follow open standards and make the overall goal to be interoperable rather than acheive dominance".
Getting Linux, or a BSD, or a BeOS workalike to take the place of windows doesn't really solve the overall problem that computing can't be simplified into a one-size-fits-all situation. A better situation is to aim for at least source-compatibility where possible (binary compatibility is nice, but largely unreasonable to expect any compatibilty layer to account for all quirks of the original host OS). If you can manage that, then things like UI become relatively easy (application framework differences are picked up at the library level, install the necessary libs and you can pick and choose your favorite, or combination thereof).
-transiit
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.
Re:Scary quote (Score:5, Interesting)
"...the new design is required to harness the increased security features of Longhorn, which Enderle said are embodied in Microsoft's "Palladium"-branded trustworthy-computing initiative.
It would seem that Microsoft cannot write a secure OS, so they are forced to rely on hardware.
"Neither Linux nor Unix ties the operating system to hardware," he said.
The way he puts it, you'd almost think it was a good thing.
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:Scary quote (Score:3, Insightful)
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: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.
Re:Scary quote (Score:5, Interesting)
The difference is that I can give my 14-year old script kiddie son a non-root account on my BSD box, and be quite certain that he does not mess with my OS installation. He can only damage his own account, which I can restore. Try that with W*nd*ws!
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.
code signing != panacea (Score:5, Interesting)
Code signing establishes identity of the signer, but it does not guarantee anything beyond that. It says, "we really think this was made by Microsoft, so if you trust them, you can trust this." Palladium may extend this trust into the hardware, but it's still reliant on the assumption that whoever signed the code is doing their homework.
There are four levels of security for software in my mind:
1) Code that is from an unverified source that I cannot look at
2) Code that is from a verified source that I can look at
3) Code from an unverified source that I can look at
4) Code from a verified source that I can look at
Ultimately any code falling into category 3 or 4 can be made secure presuming that I am knolwedgeable about security and the software I'm dealing with. Category four provides the same assurances as category two, but additionally I can further insure my security by looking myself.
Re:code signing != panacea (Score:3, Interesting)
In the land of Redmond where the shadows lie... (Score:5, Funny)
One Passport to find them,
One OS to bring them all,
And with the EULA bind them!
Sorry couldn't resist
Re:In the land of Redmond where the shadows lie... (Score:3, Funny)
Moron (Score:5, Funny)
"This could bring a higher level of security than anything we've ever seen. It will almost completely prevent the platform from being compromised."
Sounds like they will be releasing Longhorn without any networking capabilities..
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.
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: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.
error message (Score:5, Funny)
The software that you're trying to run (Doom3.exe) is not compatable with current Microsoft Standards. We at Microsoft believe that one program should "Do it all", and therefore should be integrated into the Operating System's kernel.
The integrated version of Doom3.exe will appear in your kernel once the authors of said file adapt the program for use with Direct3d.
Installation of OpenGL or any software that uses OpenGL is in direct violation of your EULA. Violation of said EULA will be severely punished.
---
Thank you for using Longhorn. There are 15 days remaining until Skynet becomes self-aware. Your extra CPU-cycles are appreciated, even if required.
Re:error message (Score:3, Funny)
BeFS (Score:3, Informative)
Creating such a file system is an extraordinarily difficult task, one that has been attempted for years by database companies, including Microsoft, but that has never reached fruition.
The BFS used in BeOS uses 64 bit addressing (18 exabytes) and has been working for over 5 years...
Re:BeFS (Score:3, Interesting)
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
And there will be one Master Ring (Score:5, Interesting)
I think Microsoft will fork itself to death.
The general rule that I see nowdays
is that people still use Microsoft
for its backwards compatability
not its new features.
Re:And there will be one Master Ring (Score:4, Interesting)
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.
Introducing Microsoft One Window™ (Score:5, Funny)
Choice quote (Score:5, Interesting)
I had to read this twice to realise that Enderle means that in a negative way. Dear god. The individual words make sense, but we're clearly not speaking the same language.
This just confirms that Microsoft's vision for future PC's really is nothing more than super-X-boxen, running only Microsoft apps. Or, app singular. And if there's a single app handling everything, it has to handle everything, so is there room for any third party software?
Further, given that the X-box is Microsoft branded right now, I wonder when Dell et al will start to wonder if Microsoft will be happy with trusting third parties to build their new toy. After all, it's all about trust, right? At what point will Microsoft decide - and start telling Joe Public - that a "Microsoft PC" is more trustworthy than an identical box built by Dell?
Re:Choice quote (Score:5, Interesting)
They're doing the work now make that a possibility. For example, Microsoft is selling network equipment now. It's very cheap stuff, but it's another cog making the "Microsoft PC" a reality. As I mentioned before, Microsoft is very motivated to do something like this -- they've already gobbled up almost all there is to eat;
The recient spike was due to the licencing change that boiled down to "pay us more now, or pay us a lot more later". Even monopolies can push thier customers so far.
So, where to go? Buy other unrelated companies? Check. Branch out into new markets (MSNBC, Xbox)? Check. Take new markets from established companies (AOL)? Check.
All I see that's left is to increase investments in unrelated companies and markets, or to take more of what they know -- PCs.
For PCs, it might take 5 years to get all the pieces together. Microsoft has the time, they have the money comming in, they don't have to do actual production, though they do have to keep an eye out for some companies to buy.
The obvious choice -- and obviously we should beware of people who use words like 'obvious' :) -- is for them to save money and wait to see what companies have the critical patents or hardware that will be important in 5 years. When it's safe, buy those companies, integrate thier product lines, promote "PC 2006" (that use those patents), and then go from there. Sell the MS PC line like Apple and Sun do, but also licence others to be resellers like they do with Pocket PC/WinCE.
If I see this as a posibility, companies that have traditionally been partners with Microsoft must see this too. Sony has already been burnt (Xbox), and just about every other large company -- from Sun through IBM-HP-Compaq-Gateway-Dell to even Intel just don't like an all-dominate Microsoft calling the shots and setting thier margins.
To save money, Microsoft only has to not issue dividends to stock holders (check), and if needed, roll that money into some other venture so that profits vanish. In 5~ years they can dump the hold over companies and use the cash to buy the critical companies.
Research and patents -- buying or making -- can be done anytime. This includes slowly inforcing the patents they have, piece by piece.
This is all speculation and guessing about the future. Before you take it seriously, go to a used book store or library and flip through books that talked about what the future would be like -- lots of grins.
The Microsoft Dream (Score:3, Funny)
Re:Choice quote (Score:3, Interesting)
I hope it does. Because then MS will follow SGI to irrelevant obscurity. Or better, let them follow DEC, since SGI still exists. Even a very well done OS, like VMS, couldn't survive being tied to proprietary hardware.
Re:Choice quote (Score:5, Interesting)
Well, quite. What - exactly - are the benefits of Palladium to various users?
Synopsis: there's only one type of user that will benefit from Palladium. Fortunately, that's the type that owns and controls everything, including IT budgets and politicians. Oh goody.
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:In market forces I trust (Score:5, Insightful)
What if :
- Microsoft discontinues W2k and XP: new PCs will come installed only with the new OS
- software and media companies release DVD, CD & such so that only works with the new OS ( because of the equation "no freedoom == no piracy")
Market works when there _is_ strong competition, the same competition that Microsoft killed in the last 20 years.Otherwise, market laws always reward the strongest, and guess who is it?Re:In market forces I trust (Score:3, Interesting)
Microsoft discontinues W2k and XP: new PCs will come installed only with the new OS
In that case
CDs only work with new OS
They are doing this sort of thing already, so nothing changes with the next version of Windows. If that business model works, they will gain market share, if it doesn't, they will rapidly find another model.
no competition
Microsoft's record on killing competition is actually rather patchy. They have cleaned up in the desktop OS and office productivity markets. They don't own the server market, they don't dominate embedded appliances, they are struggling to make the XBox work: all these ventures are losing money, which they can only afford to lose because of their market share in the first two areas.
If corporate customers start boycotting the new OS, Microsoft will back down very quickly, monopoly or no monopoly. The main reason we are still waiting for XP server is that there is resistance to the licencing model: this new system could provoke a much bigger backlash.
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: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: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:You are not taking the long view (Score:3, Interesting)
Windows is not modular
Sure. So if modularity is what matters most to me, I don't buy Windows. But you don't have to spend a cent, you just have to take responsibility for your decisions. If you want the alleged benefits of Windows, you get the alleged problems of Windows. You can have both or neither. That doesn't seem unreasonable to me.
You cannot fix a problem yourself.
At the risk of blowing any geeky aura that I might somehow have acquired, I don't fix my Linux problems either, I wait for the next upgrade, and, usually, buy a boxed version that costs me money. We have fixed some minor quirks with the perl management scripts and Apache on our RaQ, but I'm not about to start recompiling my kernel with my own bug fixes. Which relegates me to the bottom 99.99% of computer users, though I guess having the possibility to do so is a unique selling point for the other 0.01%
Everthing works with 2.2
So why did anyone upgrade, if the new one does the same thing as the old one? I'm sure I'm missing something basic here, but I thought adding useful features, improving performance etc was a good thing, even if the resulting code won't always run on an abacus. In a similar vein, it's nice that you can still get i386 rpms, but if I can get better performance out of my kit with i686 rpms, I'm going to do so.
OK, it's not quite the same thing, since the i386 ones will still do the same job. Although have you tried Star Office on a 486 with 20Mb of RAM? It runs, but the one time I tried it for a client, it took - literally - over an hour to open a blank document. I don't think this proves that Star Office is a bad program (although some other evidence points in that direction), it just shows that it is designed for more recent hardware.
If what you're saying is that the upgrade path with Linux involves more smaller steps, I'd probably agree (although if you count service packs, MS produces several upgrades a year).
Re:You are not taking the long view (Score:3, Informative)
They have - as of end of year it's no longer supported software.
It's called "remedy" for monopolization (Score:3, Insightful)
To understand the difference, see my article "Anti-globalization vs. anti-capitalism." [underreported.com]
I can see it now..... (Score:5, Funny)
I am not that worried (Score:5, Funny)
COMPANY: Does it run linux?
VENDOR: It will soon!
COMPANY: Don't let the door hit you in the ass on the way out.
Re:I am not that worried (Score:4, Funny)
COMPANY: Does it run linux?
VENDOR: We include a TechRef so you can write your own drivers and install routines to run under linux. After that, if we like your work, we'll sell it back to you as part of our price for the upgrade to the next version
COMPANY: Wonderful. You're true followers of Open Source.
Holy crap! (Score:5, Insightful)
Re:Holy crap! (Score:3, Funny)
Salesman:
Dilbert: What does it do?
Salesman: Whoa! I'm in over my head. Let me give you their tech support number.
Source: Casual Day has gone too far.
Gotta love it
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.
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.
Data oriented computing? (Score:3, Interesting)
I first noticed this back in 1985, when I bought my first Mac. On my Unix systems, the mindset is "I'm using programs to manipulate data". E.g., to change a file, I run vi (vim nowadays), and tell the program what changes I want made to the file, and the program makes the changes.
On a Mac, it feels (or, rather, it used to...Apple has moved away from this) like I'm directly making the changes. I wasn't telling MacWrite to change my file--I was changing my file, using MacWrite as my tool.
I think it felt this way because of the interface consistency among most programs. MacWrite might provide more editing options than, say, a paint program's text tool, but they were consistent. This made the programs feel like they were just part of the computer, rather than the focus of the computer like they are in Unix and Windows. The WYSIWYG aspect also certainly helped a lot.
I think that this is what Microsoft is talking about when they say one program to do everything. I doubt they mean one giant monolithic uberprogram to do everything--they've spent years moving everything in site to be collections of components, and I don't think they'll abandon that approach.
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
We are Trapperkeeper ... (Score:5, Funny)
Am I the only one who gets the image of Longhorn looking like Cartman's TrapperKeeper?
You will be assimilated ...
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"?
No worse than StarOffice (Score:3, Interesting)
Sounds a bit like that.
MS is already doing this, its called COM (Score:5, Informative)
Programming the COM in Python led me to the realization that most MS programs are just wrappers for the COM. Thats why its so easy, for example, to embed Visio drawings in Powerpoint, etc, etc.
BTW, with PythonWin you can access the MS COM directly without even starting a program. e.g. I've used the Excel functions to bring up a spreadsheet, fill it with data, and then save it, all without ever calling Excel.
Rob.
Re:MS is already doing this, its called COM (Score:5, Interesting)
You are correct, sir.
All iexplore.exe does, for example, is call mshtml.dll in creative ways. All excel.exe does is call the Excel COM objects in creative ways, and so on and so forth.
The fundamental difference between scripting on UNIX and scripting on Win32 is that on UNIX, you're manipulating text files and calling programs with CL arguments. On Win32, you're invoking objects, setting properties, then calling methods.
Comment removed (Score:5, Insightful)
giving up... (Score:3, Interesting)
no more "where is my privacy?" no more "do my actions get monitored?".
such things just make me weak, sometimes I really think that I will just lay back, accept microsofts way and be what they call a good user.
They may monitor my actions, I don't care, I got nothing to hide.
They may DRM the shit out of my PC, I don't care, I have the money to get my music legally.
In return I get an all in one solutions. I don't have to care about, just use it. And if I stick to M$ rules, the usability is going to be great. Just think about the smartphone/tabletPC/workstation connectivity. May this is a revolution in computing.
But somehow thinking like that feels like selling your sould to the devil. So what, Dr. Faust had a nice life too...
So, what do you think is getting a nice user life by giving up your freedom an option?
Microsoft Works? (Score:5, Interesting)
Personally I'm not that worried about this whole Palladium thing from MS. Windows XP has chiefly been successful because of MS' hammerlock on OEMs and because it has offered true improvements in stability over previous versions ofthe OS. I use XP every day and administer a number of XP machines and it truly has improved in stability. The flipside of the XP story is that I had to think twice before migrating there because the EULA is such a piece of capitaistic, fascist greed and fear. MS shoots itself in the foot with it's attempts to control your daily life, and in this they are truly a bunch of fucked up bastards.
I think that MS' recent financial statements showing that they are totally useless and in fact worse than many dotbombs in every single division apart from Windows and Office, offer a good insight into the true source of motivation behind MS's efforts to enforce control over hardware and users: They realise full well that no one really likes them (OEM's trying to free themselves, large companies pissed off enough to migrate to Linux) and their response is to try to tighten the screws even more. Longhorn and Palladium might very well bring improved performance and stability, but like all MS products in recent years, these improvements are mainly a sugar coating to the bitter pill of MS Palladium.
It will not work. My company does not have the money to play MS games and I will migrate everything to Linux and Novell (we already use both) beofre we go with bullshit like this. Larger companies are even more conservative than we are.
The joke is that MS could gain so many new customers and much more trust (there are people who trust them?) if they spent more efforts on simply improving their products instead of trying to fuck with everybody.
Privately I use MacOSX to develop with because the core OS is open source and the Dev tools are free and I'm fucked if I'm going to pay MS $1000 here in Switzerland for Visual Studio.
As long as the hardware isnt locked.. (Score:3, Interesting)
If we reach that point and cant get around it somehow, I know myself will be finished with computers. Almost am now with how the industry has become.
20 years ago, no one would have dreamed of what would become of it all, and the level it would reach... Makes one almost ashamed to be in the business.
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.
A failure to understand (Score:5, Interesting)
Bill Gates wants to force everyone to change the rules to deal with him and his company. Being the richest man who ever lived is not enough - like Montgomery Burns he'd "give it all up for just a little more". The little more that he wants is to be so oppressive and intrusive a part of people's lives that they are forced to change the law forever to control what he has done. He has already proven that existing monopoly laws are insufficient to keep him from doing as he pleases.
He wants to be able to answer a tech call and say: "This is Bill Gates speaking; bark like a dog - or I'll cut off your computing forever. Bark... That's a good boy." 'Trusted computing' is the last gear in the machine to allow him to do that. With trusted computing he will be able to shut down anyone at anytime; after all what power has trusted computing got except to break the machine and thus force the user to do exactly what the operating system designers want them to do? If that includes wearing a Microsoft dog collar that ties them to a particular computer - so be it.
Wow! (Score:5, Funny)
Shades of OpenDoc? (Score:4, Interesting)
The Power of XML (Score:5, Informative)
I must have missed something somewhere -- when did XML become a programming language?
Has anyone here ever worked with RTF? It's a way of adding basic font, size, layout, and color information and whatnot to a text file. You can think of it as a sort of HTML-lite. It was supposed to be cross-platform too, but Microsoft produced a version of it which was so alien that no other RTF system could handle it without preprocessing.
Now Microsoft is using XML, a cross-platform, open data markup system, and using it extensively in a proprietary, closed operating system?
XML is pretty open (at least, now anyway). What's going to make Microsoft's implementation of it "special" (in that Microsoft-special way) is the internal and proprietary XSLs which read and interpret the tags to display the information on screen and in print. Other systems can read the XML documents, but to make sense of them the way Longhorn's software will requires information that Microsoft yet again won't share.
It should be possible to recreate XSLs from the structure of the XML, which would seem to make it extremely easy to reverse-engineer. In order to prevent that, Microsoft has to "extend" XML in such a way that it breaks on other systems.
I fear for the future of XML now.
One application for everything? MS BOB! (Score:3, Funny)
Yay! I hope clippy the paper clip is an optional avatar this time.
Anyone considering buy longhorn gets what they deserve imho; but it's too bad most people have no idea about anything computer related -- and will buy anything preinstalled even if they can't even use it.
I like how all these kids on the local campus are removing XP from their machines to install win98 for example.
Mere speculation as of now.... (Score:3, Interesting)
Two Specific Points To Be Made... (Score:3, Interesting)
Did anyone else think of the 'unsinkable' Titanic when they read this? Being from the analyst or not, the arrogance in this statement alone about the command of our current technology is as scary as the statements made for the Titanic!
Two: "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."
We have this already... it's called a WEB BROWSER! From what I can determine from this statement, they are seeking to make a common shell that has 'plugins' to run different files. Just like there's a flash plugin, a Quicktime plugin, etc in browsers today. Couple this with XML and basically all they would need to do is make a base parser application that accepted a specific XSLT to deal with a specific file-type. If it does boil down to a paradigm such as this, 'software as a service' via the net would be cheap and easy bandwidth wise (all they'd have to do is download/manage an XSLT or the property MS version of one). They already have this paradigm in Office (think of an embedded spreadsheet in a word doc), so I suppose that it's nature to make this the next logical step.
Both of these statements involve putting all a user's eggs in one basket. If everything was a plugin into a master parser app, imagine having that app with a vulnerability, crashing, etc! To a certain extent I say let Microsoft do this, let Microsoft auto-download and install the latest updates, let Microsoft manage Office over the net. Why? Because the first time they have a failure (like all the problems with Hotmail/Passport a year or so back) and it brings EVERYONE down with them, they'll be in a world of hurt from their own loyal customers. The first time a hot-patch corrupts the functionality of an in house app in a Fortune 500/1000, the first time a single virus takes down all MS apps (Office, Exchange...), the first time this happens and keeps even a few big companies from using their Microsoft systems for even a few hours they're sunk. How could they not be responsible legally? And even if they weren't, imagine having to fight 1000s of 'frivolous' lawsuits in 100s of jurisdictions in 10s of countries!
Just like the LotR relation mentioned above... with one ring, everyone has one foe. And when everyone has one foe, it's easier to band together and fight said foe no matter what their strength is. So in short, go ahead Microsoft... let them take just enough rope to hang themselves!
Re:Two Specific Points To Be Made... (Score:3, Interesting)
I can vouch that this was very slow- on a 33 mhz 68040. It was also slow on a 200 mhz 604e. Around this time the project was mysteriously killed at the same time that Jobs was seeking additional support and investment from Microsoft, so it never went any farther, and it was always so technically arcane that very few people could handle developing for OpenDoc.
Anyhow, if this is what Microsoft want now, they are not inventing: only stealing from what Apple and IBM were doing AND SHIPPING years ago, and possibly from what they may have had a role in killing for everybody else. If OpenDoc had a market to operate in, by now it might have been something very amazing- I can vouch that using it led to some striking results you wouldn't expect, convenience issues that helped things happen that otherwise wouldn't. Of course, at the time it was a blow to the very concept of Office- and at the time Microsoft did not want to deprecate their cash cow, much less for some Apple/IBM product.
It's Like That Old Saying: (Score:3, Insightful)
Re:Certainly radical... (Score:3, Insightful)
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).
Re:Viruses are outdated (Score:3, Funny)
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).
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:All anti-MS, all the time (Score:3, Insightful)
Re:All anti-MS, all the time (Score:3, Interesting)
Re:Especially when you see the adds :) (Score:3, Interesting)
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.
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: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.
Yeah, and what if monkeys fly out of my butt? :) (Score:3, Interesting)
Yeow!! There goes another one. They're kinda cute, really. Once you get used to the Borg implants.
This is too early in the morning for diplomacy, I haven't had my coffee.
*
OK, OK, it *could* happen. MS has published good software in the past, which in time it felt compelled to modify and expand until it looked like a prisoner of war about to rupture from beriberi. In fairness but that should be attribute to Corporate Command, not the very bright programmers they have working there. (My college roommate was assimilated in 1989 and was very happy there. Getting rich tends to make people happy.)
I have to disagree vociferously about Outlook -- it's a ticking time bomb that has already gone off several times, yet is still installed on 3/4 of the hard drives out there. A clear example of bloat leading to unreliability, specifically irresistible evil hacker bait. Yes, I know they're finally closing the barn door, but that's not the point.
"If you're not part of the solution, you're part of management." Unk. [wayson.net] (seen on a Depressories calendar [despair.com] {recommended -- new! Demotivators})
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: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.
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.