Microsoft Ends Era Of Closed File Formats 651
RzUpAnmsCwrds writes "According to an MSDN Channel 9 interview with an Office file-format developer, the next version of Microsoft Office (Office 12) will default to newly-developed XML file formats in Word, Excel, and PowerPoint. The new formats will apparently include XML files along with other files (images, etc) inside of a Zip file. Microsoft will also be providing extensive documentation of the new format to the public through MSDN. The developer likewise announced that Microsoft would be releasing updates for Office 2000, XP, and 2003 to read and write the new formats when the new version of Office is released. If this interview is correct, it could mean the beginning of the end of Microsoft's proprietary file formats." Coverage at Beta News, Information Week, and the Washington Post.
Loosing lock-in capability? (Score:5, Interesting)
Of course this assumes that lock-in was one of their goals with a propietary format
Re:Loosing lock-in capability? (Score:2)
Re:Loosing lock-in capability? (Score:5, Insightful)
In this respect, Microsoft needs open formats just as much as anyone. Ever try to write a server-based system that reads information from DOC files? Using winword.exe with automation just doesn't really work. XML lets MS use a relatively lightweight parser in a server-based system.
Oh, and changing the default fileformat will surely spur some upgrades, but from what I've seen the corporate market is generally not in a big hurry to get onto the latest version of Office. I don't foresee a repeat of Office 97.
Last 10 years, actually. :-) (Score:2)
Re:Loosing lock-in capability? (Score:3, Informative)
Re:Loosing lock-in capability? (Score:3, Interesting)
Re:Losing lock-in capability? (Score:2)
Microsoft has lots (and lots and lots) of very very smart, motivated developers and marketers, and there is always the hope that they can begin to use those resources to build a product that really competes without resotring to bogus, short term ploys like lock-in.
Hmmm... Who turned on my "hopefulness neuron" today?
Re:Loosing lock-in capability? (Score:3, Informative)
Re:Loosing lock-in capability? (Score:3, Informative)
Lock-in continues via DRM (Score:5, Insightful)
The interesting thing is that all this server based control and logging of DMR'd functions gives an enormous boost to the type of information available for international and corporate espionage. Through backdoors, security holes or escrow keys it was possible before to get only the documents themselves for the most part. Now it's possible to monitor who's collaborating with who, and see everyone in the distribution chain.
That much can be guessed even now during the vaporware stages. However, as more technical information becomes available it will be possible to guess whether these same functions can be used for more than monitoring and can actually be used to stifle or suppress dissent or specific individuals or groups.
Re:Lock-in continues via DRM (Score:5, Informative)
It hasn't been true since at least NT4 SP6a, when NT4 achieved a C2 rating *WITH* network. Windows 2000 achieved CC both with and without networking.
The NT4 link is no longer around on MS's site, but there are still some pages out there that reference it:
Such as this one [windowsnetworking.com]
And here is Win2k [microsoft.com]
Re:Loosing lock-in capability? (Score:5, Interesting)
Re:Loosing lock-in capability? No... (Score:3, Informative)
Or not.
http://www.microsoft.com/Office/xml/faq.mspx [microsoft.com]
Re:Loosing lock-in capability? No... (Score:4, Informative)
Re:Loosing lock-in capability? No... (Score:3, Informative)
But, note that the patent and copyright provisions in the license for the Office 2003 XML Reference Schemas require you to include a notice of attribution in your program.
I'm just guessing that the GPL's noted incompatibility with an advertising clause is what breaks compatibility here. MS being MS, they could well have done it intentionally; that said, an advertising clause might also have simply been seen as appropriate. Who knows.
Re:Loosing lock-in capability? No... (Score:3, Insightful)
That said, I don't believe the GPL incompatibility was intentional; I believe it to be a side-effect of what MS thought was an appropriate way to make sure that their patents and patent issues were appropriately labeled in software using their schema.
Yes and No (Score:2, Interesting)
Re:Yes and No (Score:4, Informative)
Watch the video - the entire file format is completely open.
He admitted that inside the ZIP they are currently storing the binary copy to make it easier to test and profile against the formats, but when Office 12 is released it'll just be the one XML, completely open format. He also made a point that they are going to have 'thousands' of examples on MSDN, along with very detailed documentation and whitepapers.
Now whether it's patented or not, I don't know. But this is a _VERY_ big step for Microsoft. It's going to make translating between this and OASIS (which OpenOffice2 and a lot of others are considering/implementing as their default) as simple as an XSLT transformation.
Re:Yes and No (Score:3, Informative)
So they claim. (Score:5, Insightful)
Honestly, I am not going to believe it until I see it.
Microsoft has lied before.
It's quite possible they don't intend to open their file formats at all, they just intend to make the Washington Post and its readers think they've opened their file formats. In the meantime, if Microsoft actually wanted to "end the era of closed file formats", all they'd have to do is, you know, actually comply with the letter of the antitrust decision currently handed down against them in the E.U. and the spirit of the toothless antitrust "settlement" currently in effect against them in the U.S.. Mysteriously, they haven't.
Re:Yes and No (Score:3, Funny)
ZIP patent... (Score:3, Interesting)
Re:ZIP patent... (Score:2)
Re:ZIP patent... (Score:2)
Re:ZIP patent... (Score:2)
Re:ZIP patent... (Score:4, Informative)
gzip and zip are completely different things. gzip compresses a stream (and does a much better job than compress, which it has replaced entirely. However, gzip is slowly being replazed by bzip2 nowadays), whereas zip is an archive format that can store individual (usually compressed) files. The huge advantage of zip over compressed tar archives comes from the fact that you have random access, i.e. can extract a single file from a potentially HUGE archive).
GIF had patent issues with the LZW-Algorithm it used. The patent has expired recently, but the GIF issue is completely unrelated to ZIP (ZIP uses LZ77).
About the patent issue: There are a dozen or so zip-related patents, but they're all highly specific and shouldn't stop anyone from using zip, or even writing a zip utility. See also Patents on data compression algorithms [sc.ehu.es].
Re:ZIP patent... (Score:3, Insightful)
Actually, I don't find much of an advantage. In my experience, even if you are trying to extract a tiny file from a large archive, it still seeks through the majority of the zip file, and is only slightly faster than uncompressing the entire thing.
Despite that, tar and gzip could be even better. A little programming and you could modify
Re:ZIP patent... (Score:2)
That would be the LZW [wikipedia.org] patent held by Unisys (and IBM in some countries). You're right in that it has expired in most countries now. Gzip was made as an alternative to the Unix compress program because it used LZW, not to PKZIP. Gzip uses the LZ algorithm, which is older and slightly slower but compresses better.
Convenient... (Score:4, Interesting)
And whatever happened to Office Integrated Rights Management [microsoft.com], essentially a DRM for Office documents (New Office locks down documents [com.com]) that (of course) requires a Windows server to administer, and only works with Microsoft Office? You don't think that they're just going to let that go by the wayside, do you?
And what about patents?
Sure, OpenOffice is great, but commercial enterprises will stick with commercial solutions for which there is support. And yes, this could be built for something like OpenOffice (and indeed exists for StarOffice), just as it has been for Red Hat, but I can't see this as anything more than a much belated, empty gesture on Microsoft's part. This sums it up: "Microsoft is doing this as a way to protect its presence on the desktop." Microsoft even dug up Charles Goldfarb [wikipedia.org], "co-inventor of the concept of markup languages", for its press release to say, "Making XML the default Office file format is, for me, the culmination of a 35-year dream," Charles F. Goldfarb, the inventor of the markup language technology, said in a statement released by Microsoft. Nice touch.
Also, "Microsoft Ends Era Of Closed File Formats" is a little overreaching, don't you think? They're looking for the biggest lock-in of all with the proprietary Windows Media formats. Microsoft wants to be everywhere there is any kind of media, and it's NOT open. Boy, I can't wait to live in a world where Microsoft controls and meters content and has everyone from the end consumer to cable, satellite, and telecom operators, movie and TV production houses, and everyone in between by the balls, which is exactly what will happen if they get their way. (And submission to SMPTE *hardly* means anything. Standards are standards AFTER they've been vetted by standards bodies, have had the patent searches and pools completed, etc., and have been, you know, actually approved. Not when they've been "submitted for consideration". Further, that gesture is nothing more than an attempt to get pinhead PHB-type managers and executives on board with Microsoft when their technical underlings are pulling for open standards like H.264 - then Microsoft can shoot back to the management, Hey, we're just as open as the MPEG family of standards! Look, we even submitted our codec to SMPTE! It's not our fault they take so long to approve things! Do you really want all that H-dot-whatever-gobbledeygook that your oddball IT guys are talking about? After all, that's what *Apple* uses. You don't want an Apple technology, do you? Go with us; you know Microsoft is the right choice for your 18-million-customer cable service! [eweek.com] Utter bullshit. And ignores the fact that all of the codec improvements and tools will NOT be open; the SMPTE submission is nothing more than a thinly veiled attempt to put Windows Media everywhere as well by claiming to be "open" when they're anything but.)
Re:Convenient... (Score:5, Insightful)
That's exactly what I was thinking. If Microsoft was really opening up Office, why didn't they go for the OASIS Spec [oasis-open.org]? Me thinks that this is an attempt by Microsoft to lead the industry around by the nose, thus solidifying their place as "Industry Leader". And with a proprietary document format, they can make minor, but frustrating, changes every version just to keep the competition on its toes.
Re:Convenient... (Score:2, Insightful)
Right now, they're choosing the middle ground - opening up a format in a way that they have the upper hand and yet, folks can't fault them.
If you were a company whose motive was profit, would you really care about doing something that would make you part of the pack?
MS sees itself as being different from the pack, and so, this is a logical choice for them. It may not the perfect choice or the right one, bu
Re:Convenient... (Score:2)
I am tired of this "they're a business, they are interested in profit not xxxx". Just because they're a business it don't mean that they're free of any responsibility. They must have responsibility, and those responsibilities must be enforced by the government.
Microsoft should be punished if they attempt to lock you in so you can't have access your data (this include data made for you) unless you pay them some money. Every format should be open and available to other developers (be them open source or not)
Re:Convenient... (Score:2)
Also, I am sure there will be some features missing in the OASIS spec, and that means Microsoft has to go and lobby with OASIS to get it implemented...
all this so that other competitors can read/write its file formats much easier? Don't think so.
Re:Convenient... (Score:2)
Bullocks. We're talking about a file format for a word processor and a spreadsheet. If OOo and MSOffice can interchange formats today (not to mention all the extra "export" formats that MSOffice handles) then there's no reason why they can't follow the OASIS spec. The worst case is that MSOFfice adds a few features for some of
Re:Convenient... (Score:3, Insightful)
If MS needs extensions, that's what namespaces are for.
As long as MS extensions don't change formatting functionality (this is really not rocket science, Word is not an innovator here), they can tack whatever metadata they need into the file format and still have it be portable.
If you don't believe me, look at what Inkscape has done with SVG. Psodipodi built on it, adding a namespace to provide their needed data. Inkscape did the same on top of that. It prod
Re:Convenient... (Score:2)
Re:Convenient... (Score:4, Insightful)
I can't see this as anything more than a much belated, empty gesture on Microsoft's part.
is true from the MS perspective, but that doesn't mean nothing good can come of it. Having a documented XML format could do wonders for OpenOffice compatibility, which wouldn't necessarily put a dent in Microsoft's monopoly, but it would make life a lot easier for those of us who don't want to participate in it. I'm not saying it'll pan out, just that there are possible real benefits.
Re:Convenient... (Score:2)
Life must be interesting on your planet, Dave.
First of all, video file formats are hardly a concern of "IT" -- this is really all being hashed out in Hollywood boardrooms, and is completely offtopic in a discussion about MS Office.
Second, it really boils down to either giving Dolby a bunch of money or giving Microsoft a bunc
Re:Convenient... (Score:2)
Sure, OpenOffice is great, but commercial enterprises will stick with commercial solutions for which there is support. And yes, this could be built for something like OpenOffice (and indeed exists for StarOffice)
But thanks!
Thus to be a cynic (Score:2)
So i will belive it when i see it
MS don't seem to be that eager to open anything up , just look at the recent fun the EU courts are having
Published Specs is Not Enough (Score:2, Informative)
Remember, GIF was a completely open format -- but that didn't mean Open Source software got to use them freely.
Re:Published Specs is Not Enough (Score:2)
Nope. The NDA will forbid making a competing product.
Microsoft responding to needs of the user (Score:2)
To truly be the end of an era, they should give out the complete specs on their formats as well... I know it isn't going to happen but that would be more complete.
Re:Microsoft responding to needs of the user (Score:2)
From your post:
To truly be the end of an era, they should give out the complete specs on their formats as well... I know it isn't going to happen but that would be more complete.
From the blurb:
Microsoft will also be providing extensive documentation of the new format to the public through MSDN.
It's one thing not to RTFA ....but at least you could read the fucking headline.
XtraML (Score:2, Interesting)
Re:XtraML (Score:2)
Heard this before (Score:2)
Re:Heard this before (Score:5, Interesting)
There's XML and there's XML (Score:2)
(I say this having just gone through my semi-annual search of third-party conversion software in the neverending quest to figure out a way to get from Word documents to rationally structured XML.)
Re:There's XML and there's XML (Score:2)
I say this having just gone through my semi-annual search of third-party conversion software in the neverending quest to figure out a way to get from Word documents to rationally structured XML.
Have you tried Webworks Publisher [webworks.com]? I've had reasonable success outputting XML from Framemaker with it and I know they have a version for Word as well. It is closed/proprietary/expensive but if you are serious about converting Word docs it is worth a try. When I used it, it was somewhat buggy, but by far the best
Separate information from presentation? (Score:2)
For instance, will the format be
<font name="arial" size="18" style="bold">my heading</font>
or will it be
<heading level="2">my heading</heading>
I definitely prefer the latter (with information and presentation separated), but sadly I think it is more likely that we'll see the former.
If you have the presentation separately then it is much easier to for instance standardize a look a feel within a c
Re:Separate information from presentation? (Score:2)
If you are using the styling tools in MS Word/Excel/whatever, and applying a 'headline' style to all of the headlines, then it'll do the second.
However if you don't bother and just use the font pulldowns and size pulldown menus it will do the first.
So really, it all depends on how you set it up.
Re:Separate information from presentation? (Score:2)
<p style="Title 1">My heading</p>.
If the author hasn't used styles, you will have something like
<font name="arial" size="18" style="bold">My heading</font>
Since MS Word has to be able to read the file and associate styles with paragraphs, I don't see how they would do it without mentioning the name of the style used by a paragraph somewhere in
Re:Separate information from presentation? (Score:2)
Then I'd like a way to enforce only the use of styles.
This could be a property of the document or maybe of the template.
re-inventing the wheel (Score:2)
I'll believe it when I see it (Score:2)
No doubt it will be "open" to anybody willing to sign something saying they won't develop a competing product or tell anybody what they read, or something equally worthless. They may SAY they won't do that, but I'll have to actually see it happen to believe it and even then I'll be looking the gift horse carefully in the mouth. Any paten
Hopefully the end of .doc, etc incompatibilities (Score:3, Insightful)
Re:Hopefully the end of .doc, etc incompatibilitie (Score:2)
> Hopefully this file format change will bring about the end of ever-changing file formats from one version of an app to the next.
Somehow I doubt that the release of yet another format is going to mean the end of ever-changing formats.
Hold on a second, that's not next... (Score:2)
First, an earthquake. Then the sun must be dark as sack cloth and the moon as red as blood...and then Microsoft opens up their file formats.
The big question (Score:2)
Re:The big question (Score:2)
Consider this. (Score:5, Interesting)
Anyway, my point is that MS is making it clear that they're not threatened by competing packages, and I'm not entirely sure why not. OOo could easily replace Office for many (I hesitate to say most) users, and if we switch to totally open formats, they'll be able to interoperate without any difficulties. I'm not trying to say that OOo is in a position to hurt Office...but I'm curious if it might be. MS doesn't seem to think so, and I'm really, really wondering what makes them so nonchalant.
Catching up, but still missing OpenDocument (Score:2, Insightful)
The one thing that these others have in common, that MS Office lacks, is support for the OpenDocument [eu.int] DTD. OpenOffice.org v2 will use OpenDocument as its main format.
Note that many of the articles linked to by the original post express skepticism about how open MS' XML will actually be. Recall that in the last
Re:Catching up, but still missing OpenDocument (Score:2)
Shhhh. It's coming in a few months.
And remember, Microsoft was the first to do it. Anyone else who claims to be doing it added the feature after Microsoft did, and their version isn't as good.
You can get a virus from exporting to PDF using OpenOffice
Yeah, Right (Score:2)
ASPX runtime error (Score:2)
LMAO..
A refresh seems have it just report a generic (properly rendered) "there is a problem with the forums" page.
75% file size savings (Score:5, Informative)
Nice marketing ploy. Too bad it's a scam (Score:2, Insightful)
All kidding aside, I think any hope about this is misplaced. There will no doubt be numerous restrictions on the use of the format information.
There's also the fact that MS has
Re:Nice marketing ploy. Too bad it's a scam (Score:5, Informative)
Re:Nice marketing ploy. Too bad it's a scam (Score:3, Informative)
Just TRY to use the Office XML Specification in an Open Source application. Go ahead, I dare you.
Re:Nice marketing ploy. Too bad it's a scam (Score:5, Informative)
Looks kinda like a BSD license, don't it?
Yeah, especially the part that says "You are not licensed to sublicense or transfer your rights."
Re:Nice marketing ploy. Too bad it's a scam (Score:4, Informative)
From the FAQ [microsoft.com]:
Yay! (Score:2)
Maybe now that will end. Maybe I will be able to use the faster loading kword than OO soon too.
It will be interesting to watch the aftermath.
With document format soon to be history office applications will need to compete on price and quality.
It will be interesting to see who the winners will be with the format question out of the way.
Will quality improve? Will price improve? Will people go with whatever is cheap
Already doing it (Score:2)
I've been doing this for a while:
Yawn. This is a great idea, but not anything new. Microsoft should have done this years ago, as there is an obvious benefit to their customers and innovation is obviously moving to open formats. They would have done it earlier if they didn't need so depserately competition to spur them into action. IE7, XML Office ... what's next? Bash at the Windows DOS prompt?
Microsoft begins era of patent encumbered formats (Score:5, Insightful)
In particular; consider "Microsoft may have patents and/or patent applications that are necessary for you to license in order to make, sell, or distribute software programs that read or write files that comply with the Microsoft specifications for the Office Schemas." taken from the same page...
What changed? How is that an "improvement" exactly?
Re:Microsoft begins era of patent encumbered forma (Score:2)
Presumably, much of this is going away since they are saying the new version will be open, but what is "open" to MS may not be quite what you'd expect
Re:Microsoft begins era of patent encumbered forma (Score:3, Informative)
What about existing docs? (Score:2)
Re:What about existing docs? (Score:2)
Will office 12 include a converter? (Score:2)
Microsoft = Big Innovators (Score:2)
"Our Glorious Scientists have slashed disease rates ten times!" Yes, when you no longer sleep in your own feces and the whole ten person family doesn't eat with their unwashed hands from the same bowl, it does tend to improve hygeine.
Microsoft.dieplzkthx();
New extentions (Score:2)
Great, now I'll have people calling me up asking "what program do I use to open a 'dot D O C X' file with?"
Patents can be lost (Score:3, Informative)
However, Microsoft may be walking a tight line here (at least in theory) as they are a convicted Monopolist. I refer you to this quote from Nolo Press' "Patent It Yourself" (p 1/8), on how Patents can be lost:
"The patent owner engages in certain defined types of illegal conduct, that is, commits antitru
Re:Patents? (Score:2)
Re:Patents? (Score:4, Informative)
You fucking troll, since when microsoft's binary document formats are documented, or fast?
Implementing a file format as binary data or even a simple SGML structure such as RTF means less overhead. Using XML you have to run an XML parser, and the file is more freeform. There are no set data structures, it is just a stream of text. With a binary format you can structure it in such a way that you can read a header in and know exactly where to seek in the file to get the information you need. With XML you are pretty much stuck reading sequentially and figuring things out as you go along. Sure, an XML parser library may make it easier, but behind the scenes it is still parsing that stream and processing each tag one at a time.
Re:Patents? (Score:4, Informative)
A well-designed binary format makes much more sense than XML, in this I concur with you, but XML is better than current microsoft's doc formats in that it would be easier to figure out the inner workings of the format, and making struggle for compatibility a much less gory task.
Re:Patents? (Score:3, Insightful)
Oh puuuulllleeze.
Such concerns might be relevant for a C64 or perhaps even a MacPlus. However, for small consumer documents such notions are absurd.
This isn't exactly someone's corporate data warehouse we're talking about here.
Re:Patents? (Score:3, Informative)
Take a look at a high school senior's Publisher & PowerPoint files some time. They are HUGE, especially with lots of pictures (as instructed). It's not unusual to see file sizes 100-250mb on an ordinary PP or Pub file. And boy do they take a long time to open across a network on P4 computers with lots of ram. We just had a graduation PowerPoint file that was in the neighborhood of 700mb and it took a co
Re:Patents? (Score:2)
Re:Patents? (Score:5, Insightful)
I use Open Office exclusively and have for the past couple of years. Reading the files in certainly isn't a problem for me. The only files that are slow to load are the master document files, and that's because they link to dozens of other files.
The XML specification is being expanded (it might already be done) to allow binary formats. There are good reasons, though, why it's best to keep data files in straight XML text format. It eliminates the need to worry about machine architecture. Little endian or big endian, it maks no difference to you. The files are perfectly portable across platforms, which is increasingly important these days. XML files zip very nicely, making them almost as small as a corresponding binary file.
It is far easier to provide backwards compatability to earlier file formats when you are using XML than if you are using binary file formats. With XML, if it sees a tag it doesn't understand, the parser ignores it. If a binary file format loader sees stuff it doesn't understand, it bails out with an illegal file format error.
When you move to a new expanded file format with XML, you don't have to write a conversion utility. Since you are merely adding new tags, your program can read any of your old data just fine, then add the appropriate tags and new data. This saves a great deal of trouble for programers.
Machines are fast and cheap. People are slow and expensive. It is far better to have our computers do a little extra work on loading a text file and eliminate conversion utilities and complicated loading routines that a prone to bugs.
Visual Diff of application files (Score:3, Insightful)
One of my favourite features of XML vs. binary application files is that, if you run diff on two XML files -- say, SVG drawings --, you can actually read how that drawing has been changed, just like with code or any other text file. It gets difficult to visualise on larger changes of course, but that's not unlike code either. I think, if people start
Re:Patents? (Score:3, Insightful)
The term you are looking for here is 'self describing structure'.
If you have data in the form of LISP S-Expressions you know where structures start and stop. If you have just one document in that format you can pretty much work out the entire file format - or at le
Re:Patents? (Score:2)
Great. Now we have a bloated XML-format instead of a fast documented binary-format.
A lose-lose situation.
This will make Office as slow as cOOpycatOffice.
Good job, morons. Dig your own grave.
Good job, moron. Post as absolutely ignorantly as possible.
1)Where is this alleged "fast documented binary-format[sic]"? I haven't seen it.
2)What information do you have that suggests that the XML format will be bloated?
3)Even if we take 1 and 2 as given, I only see one "lose" what's the "lose-lose" about?
Re:Patents? (Score:3, Interesting)
While VB.Net has its admirers, I think Mono was more a response to the need to interoperate and prevent MS from taking over Net apps development and locking it in to MS languages, more than it was any "admiration".
Re:Patents? (Score:3, Interesting)
(Disclaimer: They might be using it, but TFA doesn't mention it and it wouldn't fit with their MO.)
Re:Own Goal? (Score:2)
not that its a bad thing... I just think this is their real motives..
Re:Existing formats? (Score:2)
1.) Stop OpenOffice migrations (why migrate when we can just wait for MS to come out with their solution and we'll just buy that)
2.) Get people to upgrade to the next Office.
#1 is typical of MS - promise something, people wait, your competition can't survive when their business dries up, then you kill the project. Problem is, this isn't a pay-for product, so it's not going to go away.
#2 is the real thing - people will buy the next version of office, which is a huge problem
Re:Sheesh (Score:2)
More like "Microsoft states that it is doing something Slashdot has wanted them to do for ages [open up their formats in such a way that they compete on a level playing-field and compete on merit, rather than lock-in plus the network effect], and slashdot finds the faults that show that Microsoft are in fact doing no such thing".
Re:Sheesh (Score:2, Informative)
Leaving aside that fact that, like you, Slashdot is not an intelligent entity with needs and desires, this is not what we wanted.
We want an open, documented and non-patent encumbered format that allows interoperability between Office and other software.
That is not what this is.
Another poster has already provided a link that will tell you everything you need
Re:Open Office might benefit... (Score:2)
You can't let these Open Source junkies get in the way of REAL productivity. Their "Something for nothing" mentality is absurd. You get what you pay for, and something that's free clearly isn't good enough to justify charging money.
And considering some of the crap the charge money for, that's saying something.
Microsoft all the way baby. Microsoft all the way.