Microsoft Renovates Office Suite as a Web Service
foobsr writes "According to an article in EcommerceTimes, Microsoft is trying to migrate Office from a product to an online service with a focus on automating collaborative work. Quote: 'Making collaboration faster, easier and more efficient will be the next revolution in worker productivity, and we want to be in the forefront,' said Peter Rinearson, vice president for new business development in Microsoft's information worker group"."
But for Microsoft, which is starting to see its growth slow, reinventing that suite of old reliables including Word, Excel and PowerPoint has become nothing less than a key to its future.
Umm.... Yeah. I remember when MS finally decided to get on the Internet bandwagon, and started putting "Internet functionality" in every single one of their applications. Remember how poorly that was implemented, and how little of value they were actually able to add to the various Office apps?
I don't see this as being much different. Buzzwords, ooh-ahh's from the PHBs, but little increased value for the end user. Collaborative PowerPoints? Um... Ok. Isn't that what source code control systems are for, even for binaries? Pure vaporware, baby. I mean look at this:
The new design makes programs like Word, Excel and Outlook e-mail part of collaborative work spaces. In theory, an employee working in Word could tap into all the corporate information on a customer or project.
What? What the heck does that even mean? Sounds like they're dreaming about some sort of uberlayer on top of all Office apps that will let you somehow get information no matter where it's stored. AND do it collaboratively.
*cough*
Righty-o. Believe it when I see it, chappies.
Pretty soon, Office will look like Lotus Notes.
Oh joy.
---- The above post was generated by the Turing Institute. Maybe.
So now you don't have to worry about skript kiddies making your computer go "beep beep" and deleting like HALF of your report.
Now it will be deleted every 5 minutes and the save-as function won't work. But that's a feature.
Inovation!
Not a Twitter sockpuppet... but I wish I was.
And we want you to give Microsoft a copy of all of your important business documents. Who could think that was not a good idea?
I'm an American. I love this country and the freedoms that we used to have.
Oh great, the two biggest nightmares that exist in the Slashdot crowd are about to combine: Clippy and ActiveX.
AAAAAAAAAHHHHHHHHHHHHHHHHHHHHHHH!
It would be cool if it didn't suck.
...since according to the article:
"Because the next version of Windows, called Longhorn, may not ship until 2007, analysts say, the Office overhaul is needed in the meantime to deliver more Web services technology to the desktop. The new capabilities in the Office system are also needed to lure software developers to create more applications that run on Microsoft products."
If they can't reinvent Office, and their next version of Windows won't be out until 2007, their income streams will dry up and they'll need to tap into their cash reserves, which I'm sure is the last thing they want to do.
Find out about the Lexus Rx400h Hybrid!
No, you'll call it inovating, they'll call it innovating :)
Disconnect and self-destruct, one bullet at a time.
Since people would probably stop buying newer versions of Office because they won't offer much productivity increase, I think this is a way to force people to keep paying money for Office.
This is not new. I was at a conference over two years ago and heard a talk about .net from some MS developer. Every other word out of his mouth was "software as a service".
What I took home from this was the notion that MS wanted to migrate everything they do to web services... why?
They claim it's because all updates will happen automatically and be transparant to the user.
My theory is that it's really because it gives them total control over what you can do. You will never own anything. Just rent the service. You will always be trapped in the "pay your MS tax or you can't even open your own documents" nightmare. What a terrible plan for the users.
Microsoft needs to realise that Office is firmly fixed in the minds of 99 percent of its user base as an word processor/spreadsheet/presentation graphics/database/email client suite. It wouldn't matter if they bolted a space shuttle onto it, as far as the overwhelming majority of people would be concerned, it would still be all about Word, Excel, PowerPoint, Access and Outlook.
Trying to leverage Office into other roles is not going to work. Yes, some people will make use of a web service feature but it will go virtually ignored by all but that tiny fraction that tries out everything new Office paradigm because Microsoft tells them that it's the best thing since sliced bread.
Office users get what they want out of Office right now. They're happy sharing documents by email and other means. So why would they and their organisations throw all that away and take the time, effort and money to implement a web services-orientated approach? Who wants to explain to the CEO that he's got to stop asking people to email him documents and start asking them to publish them, and that he's got to do the same with his own output too? Who wants to retrain all their end-users to this new way of thinking?
Microsoft has a real problem right now with its Office suite and it knows it. It's not that Office doesn't work, it's that it works too damn well: what virtually every Office user wants to do document-wise has been possible for quite some time now.
There's very little that Microsoft can do to the individual applications to improve them by delivering new features with tangible benefits, and certainly the applications in Office XP weren't significantly better than those in Office 2000, so it's obsessed with "improving" Office by trying to manage how people work. This kind of improvement might deliver results in Microsoft's labs but in the real world, where people are resistant to change and have a "if it ain't broke, don't fix it" attitude, it's doomed to failure.
"Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
subscription based services. This is a step in that direction. Microsoft is scrambling for a way to get people to 'subscribe' to office because they ran out of features worth upgrading for with office 97 (well, for probably 80% of thier users anyway, and that 20% isn't gonna sustain the growth shareholders have come to expect).
:).
I don't see the benefit to this for anyone but Microsoft. I don't think the Internet could handle 250 million people 'streaming' office. Which means something's gonna get installed, and it's gonna be just as much a pain to fix when it breaks as the current office. Oh well, maybe crap like this will encourage openoffice.
Off topic, but I've notice a funny trend in office suites. I'm seeing more and more people running openoffice because their computer got laid waste by a virus, and they didn't get any CDs from thier OEM (or lost em). Buying office without buying a computer isn't an option for most people, so they're driven to oo.org
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
Kinda makes you wonder what reverse engineers, keygen programmers, and software crackers are going to do when they have to pirate a web service instead of a normal app.
How will this be a good thing for people who don't need the collaborative tools? It seems this is not just about collaboration; it is also about taking Office off of the desktop and putting it on the web where user registration can be more tightly controlled, upgrade paths more easily enforced, etc. And while I'm sure there will be encryption, do you really want all the data you input to office programs flying across the web? Perhaps I am misunderstanding what they mean by "web service" here -- but it sounds like they want the application on their server and the user is always a client. I don't know if I trust the MS server with that much access to my data.
Office and SharePoint 2003 have begun this move. It is not turning into a web service as the summary suggests, but instead utilizing web services for collaboration.
The company I work for has been using SharePoint for Issue tracking in our software applications for nearly a year. It was way easier to setup and use than bugzilla and several other free alternatives. And the issue tracker is a very secondary feature of SharePoint!
It allows the creation of document libraries that can associate arbitrary metadata with documents. When you save a document from an Office application is can actually be saved directly to the SharePoint document library (you can browse to the web page in the save as dialog and it shows a little html based page right in the mini-explorer and you can save there like a normal file). After clicking save, if the document library has been extended with metadata (by any non-tech-savvy user) you are prompted to enter that data.
You can also create document workspaces which are document libraries that have an associated message board, contacts list, task list and other odds and ends. All of that information appears in a sidebar in any office application which lets you instant message, email, or assign a task to a contact related to the document you are working on. Documents in any type of document library allow for versioning and check-in/out functionality.
InfoPath is probably the coolest Office application when it comes to collaboration. If you fill out an InfoPath form, the xml output can be funneled into a SharePoint document library which can calculate statistics from the documents and sort/organize them for you.
Its only the first version of the Office System that uses this functionality, and we all know it takes Microsoft 3 tries to get anything just right. Luckily, the system works well on the first try, I can't wait for the third attempt!
http://brandonbloom.name
Many programs need to work on operating in a collaborative environment.
Do you have any idea how very nearly impossibly difficult this sort of thing is? It makes The Theory of Relativity look like a stroll on the beach.
Indeed, the sorts of problems encountered [when concepts like "TRUE" and "FALSE" cease to have meanings independent of their times and places] bear more than a passing resemblance to The Theory of Relativity.
Think I'm kidding? Try reading the RFC for the Network Time Protocol:
All that NTP seeks to do is get two computers to engage in the most fundamental task of computing: Come to some reasonable agreement as to the time. And yet, the RFC requires just about a PhD in mathematics and about 1000 pages of background reading from old AT&T switching standards just to begin to get an idea of what the heck is going on.The first thing to realize is that a web service no longer indicates internet anymore. It's a shift in paradigm. It's time for a lot of you guys to throw out your blue polyester shirts and suspenders. Web simply means it's delivered from a central location and typically works through a browser or derivative of a browser. This doesn't mean 2 billion users will be streaming office from microsoft.com. It doesn't mean that when MS's servers go down that the entire world will be without Office.
.NET reaches full maturity and is available for other platforms. Realistically, Linux might be running MS office in the near future.
This is simply the realization of the thin client paradigm. As corporate environments go, it's about time.
And before anyone panics about all those stand alone machines out there (like us developers are all so fond of), there are a bunch of appies out there that are essentially written this way already. VS.NET is web driven. That front end is all xml/html driven. We see it with the MS management console and MSC snappins for it too. This is the sort of thing we're looking at with the future of office.
The front end will be web based. The back end will likely have a few different options and standalone on the local machine I would wager will still be one of them. But at the same time, the back end could be centralized greatly simplifying mangement. I wouldn't be suprised if the next incarnation of Visual Studio can be set up to compile on a central server.
This should in theory simplify development of the Office software and reduce all versions of Office to a single codebase once
Now, instead of accomplishing things, workers can have interminable interactive discussions over the most incredible minutia with their bosses.
If you thought clippy was annoying, just wait until MS Office allows your boss to pop up in a little window on the screen and interrupt whenever you're in the middle of something.