Group items matching

in title, tags, annotations or url

I've pretty much stayed out of the EU action against Microsoft primarily because it misses the mark by so much. The browser is not the means by which Microsoft seeks to create a Web based monopoly. MSIE is a useful tool used to frustrate Web developers and systems providers, but we are way beyond the point where removing/replacing MSIE becomes an effective remedy to Microsoft monopolist abuses. Way beyond! There is however no doubt in my mind that the browser is going to be the portable WebOS of the future. The problem is that browser runtimes are also host for proprietary runtime plug-ins. Like MS Silverlight! Read on freind. My comments are three part, and posted down the line, somewhere around 183. Heavy on the WebKit stuff as usual! Look for "gary.edwards".

Last week, Microsoft reported that revenue from the Microsoft business division (MBD) grew 20% year over year to US$4.95 billion in the most recent quarter. That is more than Microsoft's client division, which makes Windows. Most of MBD's revenue comes from Office, though Microsoft doesn't break out an exact percentage. Windows has 1 billion users. Office has only 500 million. Consumers will be able to subscribe to Office Web and even get it at a discount price, provided they are willing to view Web ads. Business customers seeking "more manageability and control" will be able to buy subscriptions to Office Web similar to the subscription Microsoft offers for a bundle combining Web-based versions of Exchange and SharePoint. That costs $3 per user per month. Enterprises may also get Office Web through conventional volume licensing software contracts, which will allow them to either install Office on desktop and other client PCs, or have Microsoft host it on their server. Unlike non-Microsoft products (Google Docs - ZOHO - BuzzWord), Office Web will guarantee that the "viewing experience is fantastic" and that formatting and meta data from Office documents don't "get munged up,". Office Web will provide a superior "end-to-end solution" by letting users view and edit documents whenever they want to, including browsers such as Firefox, Internet Explorer and Safari and Windows Mobile smart phones. The Office Web focus will be on business productivity according to Chris Capossela. The Office Web experience can be enhanced by Silverlight (Microsoft RiA).

Matt Assay has posted an interesting article arguing the point of view that Google Chrome will have a difficult time catching up Microsoft SharePoint. While everyone is moving to the Web, many will be surprised ot find that Microsoft is already there. Very surprised.

Good article from Matt Assay

Good analysis by Stephen Vaughan-Nichols. He gets it right. Sort of. Stephen believes that Chrome is desinged to kill MSOffice. Maybe, but i think it's way too late for that. IMHO, Chrome is designed to keep Google and the Open Web in the game. A game that Microsoft is likely to run away with. Microsoft has built an easy to use transiton bridge form MSOffice desktop centric "client/server" computing model to a Web centirc but proprietary RiA-WebStack-Cloud model. In short, there is an on going great transtion of traditional client/server apps to an emerging model we might call client/ WebStack-Cloud-RiA /server computing model. As the world shifts from a Web document model to one driven by Web Applications, there is i believe a complimentary shift towards the advantage Micorsoft holds via the desktop "client/server" monopoly. For Microsoft, this is just a transtion. Painful from a monopolist profitability view point - but unavoidably necessary. The transition is no doubt helped by the OOXML <> XAML "Fixed/flow" Silverlight ready conversion component. MS also has a WebStack-Cloud (Mesh) story that has become an unstoppable juggernaut (Exchange/SharePoint/SQL Server as the WebSTack). WebKit based RiA challengers like Adobe Apollo, Google Chrome, and Apple SproutCore-Cocoa have to figure out how to crack into the great transition. MS has succeeded in protecting their MSOffice monopoly until such time as they had all the transtion pieces in place. They have a decided advantage here. It's also painfully obvious that the while the WebKit guys have incredible innovation on their side, they are still years behind the complete desktop to WebStack-RiA-Cloud to device to legacy servers application story Microsoft is now selling into the marketplace. They also are seriously lacking in developer tools. Still, the future of the Open Web hangs in the balance. Rather than trying to kill MSOffice, i would think a better approach would be that of trying to

There are five reasons why Google is doing this, and, if you read the comic book closely - yes, I'm serious - and you know technology you can see the reasons for yourself. These, in turn, lead to what I think is Google's real goal for Chrome.

I'm still keeping the door open on a suspicion that Microsoft may have planned to end the life of MS Office after the new fortress on the server side is ready. The code base is simply too brittle to have a competitive future in the feature wars. I can't get past my belief that if Microsoft saw any future in the traditional client-side office suite, it would have been building a new one a decade ago. Too many serious bugs too deeply buried in spaghetti code to fix; it's far easier to rebuild from the ground up. Word dates to 1984, Excel to 1985, Powerpoint to 1987, All were developed for the Mac, ported years later to Windows. At least Word is still running a deeply flawed 16-bit page layout engine. E.g., page breaks across subdocuments have been broken since Word 1.0. Technology designed to replace yet still largely defined by its predecessor, the IBM Correcting Selectric electro-mechanical typewriter. Mid-80s stand-alone, non-networked computer technology in the World Wide Web era? Where's the future in software architecture developed two decades ago, before the Connected World? I suspect Office's end is near. Microsoft's problem is migrating their locked-in customers to the new fortress on the server side. The bridge is OOXML. In other words, Google doesn't have to kill Office; Microsoft will do that itself. Giving the old cash cow a face lift and fresh coat of lipstick? That's the surest sign that the old cow's owner is keeping a close eye on prices in the commodity hamburger market while squeezing out the last few buckets of milk.

"Just as we have an operating system for the PC, for the phone, and for the server, we need a new operating system that runs in the Internet,".... "Windows Cloud will be a place where you can run arbitrary applications up in the Internet that runs .NET." ..... "a shift in Microsoft's overall developer tools, means putting .Net in the browser, which we've done with our Silverlight technology," Ballmer said.... "PC applications have better user interface, and you can integrate them more. Browser applications run on non-Windows machines, and they're easier to manage. We need to bring the benefits of both of those things together on Windows, and through our Silverlight technology permit the targeting of other systems."

Response to ZDNet article about Lotus Symphony and OpenOffice. Dana gets it terribly wrong, claiming that Lotus Symphony is "open Source". I respond by setting the record straight. Couldn't help myself though. I dove into the whole "rip out and replace", government mandates, ODF vs. OOXML thing. ending of course with the transition from client/server to client/Web-Stack/server and the future of the Web.

Like this http://www.hdfilmsaati.net Film,dvd,download,free download,product... ppc,adword,adsense,amazon,clickbank,osell,bookmark,dofollow,edu,gov,ads,linkwell,traffic,scor,serp,goggle,bing,yahoo.ads,ads network,ads goggle,bing,quality links,link best,ptr,cpa,bpa