Group items tagged

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.

Two former Microsoft employees have started a company aimed at making Microsoft Office more like Google Docs - at least on the online-collaboration front. DocVerse - a stealth startup formed by Shan Sinha, a former Microsoft SharePoint and SQL Server strategist, and Alex DeNeui, also formerly involved with SQL strategy at Microsoft - has begun offering beta invitations to a few hundred interested testers.

Bamboo has cracked MOSS, releasing a free data integration service called "MashPoint". Very cool. Espeially interesting are all the Windows Services exposed by the crack! For anyone trying to understand the depth of connectivity between the Windows MSOffice-Outlook desktop and the MS Web-Stack (Exchange-SharePoint-SQL SErver), Bamboo MashPoint is a great place to start.

Visit News www.killdo.de.gg. How to make the 1000 visitor from PR9 backlinks. Buy cheap service www.fiverr.com/radjaseotea/making-best-super-backlink-143445

The question that seems more important than all the rest is "Can I afford to switch vendors?" Let's consider some examples. When printers wear out, you can buy new printers from whoever with little concern for switching cost. If you're unhappy with your current servers, you can replace them with models from lots of vendors (Sun, Dell, HP, IBM, others) without worrying too much about compatibility (well, you may have some racking and cabling pain); the issues are price, performance, and support. If you're grouchy about your OS, you can move between *n*x flavors like Debian, SUSE, and Solaris pretty freely in most (granted, not all) cases; with maybe some deployment and sysadmin pain. If you're unhappy with your desktop environment, well too bad, you're stuck. Your users are too deeply bought into some combination of Outlook calendaring and Excel macros and Sharepoint collab. The price of rebuilding the whole environment is simply too high for most businesses to consider. If you're unhappy with your Oracle licensing charges, you probably have to suck it up and deal with it. SQL is a good technology but a lousy standard, offering near-zero interoperability; the cost of re-tooling your apps so they'll run on someone else's database is probably unthinkable. Like they say, you date your systems vendor but you marry Larry Ellison.

"By combining unified communications, IM, SharePoint, and blogs and wikis while protecting its IP, Monsanto is advancing teamwork." InformationWeek has posted a number of technology innovation-implementation profiles. Monsanto is one of the best "collaborative" examples, although it's very similar to the model GE presented at Office 2.0. These colalborative concepts go back 1998, and the early work Ars Digita was doing with the first "Knowledgeware" - wiki applications. The first "use case" to be published was that of the global electronics giant, Siemanns. Notice the SharePoint - MSOffice integration as a key element in the Monsanto collaboration strategy. That connection "forced" Monsanto to rebuild their document databases and portals using SharePoint and SQL Server.

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