Skip to main content

Home/ Document Wars/ Group items tagged Microsoft-Cloud

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

Microsoft opens Outlook format, gives programs access to mail, calendar, contacts - 0 views

www.computerworld.com/...cess_to_mail_calendar_contacts

Microsoft Outlook interop de facto standards

shared by Paul Merrell on 28 Oct 09 - Cached
  • Microsoft on Monday said it will provide patent- and license-free use rights to the format behind its Outlook Personal Folders opening e-mail, calendar, contacts and other information to a host of applications such as antimalware or cloud-based services.
  • Documenting and publishing the .pst format could open up entirely new feature sets for programs such as search tools for mining mailboxes for relevant corporate data, new security tools that scan .pst data for malicious software, or e-discovery tools for meeting compliance regulations, according to Microsoft officials.
  • Paul Merrell on 28 Oct 09
     
    The ripples from the European Commission v. Microsoft decision continue to flow. The catch, of course, is that the patent rights will almost certainly be subject to the Microsoft Open Specification Promise, a weasel-worded document that actually grants no rights. http://law.bepress.com/unswwps/flrps/art71/ But someone with some clout will push that issue sooner or later.
Gary Edwards

Microsoft Leaves Ballmer Bleeding as It Moves On - 0 views

www.cmswire.com/...ding-as-it-moves-on-026254.php

wordsdk Office-365 Cloud-Productivity-Platform

shared by Gary Edwards on 20 Aug 14 - No Cached
  • Nadella has only been in there six months and his daring — daring for Microsoft, that is — is breathtaking. He has released Office for iPad, which rumor has it was developed under Ballmer, but kept in storage for fear that it would impact on Microsoft’s Office business.
  • Office 365 has also been opened up and he has made its roadmap transparent, enabling enterprises plan where their productivity spending will go.
  • Gary Edwards on 20 Aug 14
     
    "the road that Nadella chose marked a shift in direction from the old Microsoft. Nadella has only been in there six months and his daring - daring for Microsoft, that is - is breathtaking. He has released Office for iPad, which rumor has it was developed under Ballmer, but kept in storage for fear that it would impact on Microsoft's Office business. Nadella also oversaw the release of a free version of Windows for devices that had screens less than nine inches. On top of this he changed the entire release cycle for Windows by announcing regular upgrades as soon as they are developed, and not as a single major release once a year. Office 365 has also been opened up and he has made its roadmap transparent, enabling enterprises plan where their productivity spending will go."
Gary Edwards

Consumer Office 365 tops a half-billion dollars in annual revenue run-rate - Computerworld - 0 views

www.computerworld.com/...ars_in_annual_revenue_run_rate

wordsdk Office365

shared by Gary Edwards on 12 Aug 14 - No Cached
  • In the June quarter, Microsoft added approximately 1.2 million subscribers to its consumer Office 365 rolls, a quarter-over-quarter growth rate of 27%, but a year-over-year increase of 460%.
  • Microsoft's Office 365 "rent-not-buy" subscription service is at an annual revenue run-rate of more than half a billion dollars, Microsoft signaled last week.
  • According to CFO Amy Hood, Microsoft ended the June quarter with more than 5.6 million Office 365 subscribers to its consumer-grade plans, labeled "Home" and "Personal." The former sells for $100 annually, while the latter -- which was introduced in mid-April -- lists for $70 a year.
  • ...3 more annotations...
  • Microsoft's quarter-over-quarter gain was 100%,
  • Pacific Crest Securities said it anticipated 1 million new consumer subscribers per quarter. If Pacific Crest's forecast is accurate, the quarter-over-quarter gain for the three months ending Sept. 30 would be about 18%, but would represent year-on-year growth of 230%.
  • Nor would Microsoft assign credit for Office 365's gains -- whether on the consumer or commercial side -- to any specific move it has made, including the release of Office for iPad in March. When a Wall Street analyst asked Hood about the source of a large gain in cloud revenue -- which includes Office 365 for businesses -- and if Office for iPad played a part, the CFO declined to name any one factor. "I wouldn't point to one product area," Hood answered.
  • Gary Edwards on 12 Aug 14
     
    "Microsoft's Office 365 "rent-not-buy" subscription service is at an annual revenue run-rate of more than half a billion dollars, Microsoft signaled last week. According to CFO Amy Hood, Microsoft ended the June quarter with more than 5.6 million Office 365 subscribers to its consumer-grade plans, labeled "Home" and "Personal." The former sells for $100 annually, while the latter -- which was introduced in mid-April -- lists for $70 a year. "
Gary Edwards

WebODF - 1 views

webodf.org

WebODF WebKit HTML+

shared by Gary Edwards on 01 Jun 11 - No Cached
  • Gary Edwards on 01 Jun 11
     
    WebODF is a JavaScript library that makes it easy to add Open Document Format (ODF) support to your website and to your mobile or desktop application. It uses HTML and CSS to display ODF documents. WebODF is a Free Software project. All code is available under the AGPL. This means that you can use the code free of charge, investigate how it works, and share it with others. Description of WebODF From LWN: ODF on the web An especially interesting project that was presented is WebODF, which wants to bring ODF to the web. Jos van den Oever started from the observation that a lot of office suites are moving into the "cloud". Examples are Microsoft Live Office, Google Docs, and Zoho. But where are the free software alternatives for the cloud? For OpenOffice.org, KOffice, AbiWord, and Gnumeric, there are none that have a cloud version with ODF support. That was the motivation for Jos to start a project to fill in this gap and let users view and edit ODF documents on the web without losing control of the document into some company's servers. The strategy Jos followed was to use just HTML and JavaScript for the web application. The application then loads the XML stream of the ODF document as is into the HTML document and puts it into the DOM tree. Styling is done by applying CSS rules that are directly derived from the and elements in the ODF document. That is how WebODF was born; it is a project with the initial goal of creating a simple ODF viewer and editor for offline and online use, implemented in HTML5. The small code base consists of one HTML5 file and eight JavaScript files, each of which is a few hundred lines of code. The most interesting part is that it doesn't need server-side code execution: the JavaScript code is executed in the user's browser and saving the document to the web server is done using WebDAV. It supports both the Gecko and WebKit HTML engines. There is also an implementation on top of QtWebKit, which is
Gary Edwards

ODF and OOXML - The Final Act - 0 views

www.idm.net.au/story.asp

din fraunhofer harmonization iso odf ooxml opendocument openxml

shared by Gary Edwards on 04 Feb 08 - Cached
  • The format war between Microsoft’s Open Office XML (OOXML) and the open source OpenDocument Format (ODF) has flared up again, right before the looming second OOXML ISO vote in March.
  • “ISO has a policy that, wherever possible, there should only be one standard to maximise interoperability and functionality. We have an international standard for digital documentation, ODF,” IBM’s local government programs executive Kaaren Koomen told AustralianIT.
  • ODF has garnered some criticism for being a touch limited in scope, however, one of its strengths is that it has already been accepted as a worldwide ISO standard. Microsoft’s format on the other hand, has been criticised for being partially proprietary, and even a sly attempt by the software giant to hedge its bets and get in on open standards while keeping as many customers locked into its solutions as possible.
    • Gary Edwards
      Gary Edwards on 04 Feb 08
       
      A "touch limited in scope"? Youv'e got to be kidding. ODF was not defined to be compatible with the billions of MSOffice binary (BIN) documents. Nor was it designed to further interoperability with MSOffice.
      Given that there are over 550 million MSOffice desktops, representing upwards of 95% of all desktop productivity environments, this discrepancy of design would seem to be a bit more than a touch limited in scope!
      Many would claim that this limitation was due to to factors: first that Microsoft refused to join the OASIS ODF TC, which would have resulted in an expanded ODF designed to meet the interoperability needs of the great herd of 550 million users; and second, that Microsoft refused to release the secret binary blueprints.
      Since it turns out that both IBM and Sun have had access to the secret binary blueprints since early 2006, and in the two years since have done nothing to imptove ODF interop and conversion fidelity, this second claim doesn't seem to hold much water.
      The first claim that Microsoft didn't participate in the OASIS ODF process is a bit more interesting. If you go back to the first OASIS ODF Technical Committee meeting, December 16th, 2002, you'll find that there was a proposal to ammend the proposed charter to include the statemnt that ODF (then known as Open Office XML) be compatible with existing file formats, including those of MSOffice. The "MSOffice" reference was of course not included because ODF sought to be application, platform and vendor independent. But make no mistake, the discussion that day in 2002 was about compatibility and the conversion of the legacy BIN's into ODF.
      The proposal to ammend the charter was tabled. Sun objected, claiming that people would interpret the statement as a direct reference to the BIN's, clouding the charter's purpose of application, platform and vendor independence. They proposed that the charter ammendment b
    • Gary Edwards
      Gary Edwards on 04 Feb 08
       
      Will harmonization work? I don't think so. The problem is that the DIN group is trying to harmonize two application specific formats. OpenOffice has one way of implementing basic document structures, and MSOffice another. These differences are directly reflected in the related formats, ODF and OOXML. Any attempts to harmonize ODF and OOXML will require that the applications, OpenOffice and MSOffice, be harmonized! There is no other way of doing this unless the harmonized spec has two different methods for implementing basic structures like lists, tables, fields, sections and page dynamics. Not to mention the problems of feature disparities. If the harmonized spec has two different implementation models for basic structures, interoeprability will suffer enormously. And interoperability is after all the prupose of the standardization effort. That brings us to a difficult compromise. Should OpenOffice compromise it's "innovative" features and methods in favor of greater interoperability with MSOffice and billions of binary documents? Let me see, 100 million OpenOffice installs vs. 550 MSOffice installs bound to workgroup-workflow business processes - many of which are critical to day to day business operations? Sun and IBM have provided the anser to this question. They are not about to compromise on OpenOffice innovation! They believe that since their applications are free, the cost of ODF mandated "rip out and replace" is adequately offset. Events in Massachusetts prove otherwise! On July 2nd, 2007, Sun delivered to Massachusetts the final version of their ODF plug-in for MSOffice. That night, after reviewing and testing the 135 critical documents, Massachusetts made a major change to their ETRM web site. They ammended the ETRM to fully recognize OOXML as an acceptable format standard going forward. The Massachusetts decision to overturn th
  • ...1 more annotation...
    • Gary Edwards
      Gary Edwards on 04 Feb 08
       
      The Burton Group did not recommend that ISO recognize OOXML as a standard! They pointed out that the marketplace is going to implement OOXML by default simply because it's impossible to implement ODF in situations where MSOffice dominates. ISO should not go down the slippery slope of recognizing application-platform-vendor specific standards. They already made that mistake with ODF, and recognizing OOXML is hardly the fix. What ISO should be doign is demanding that ODF fully conform with ISO Interoeprability Requirements, as identified in the May 2006 directive! Forget OOXML. Clean up ODF first.
  • Gary Edwards on 04 Feb 08
     
    Correcto mundo! There should be only one standard to maximise interoeprability and functionality. But ODF is application specific to the way OpenOffice works. It was not designed from a clean slate. Nor was the original 2002 OpenOffice XML spec designed as an open source effort! Check the OOo source code if you doubt this claim. The ONLY contributors to Open Office XML were Sun employees! What the world needs is in fact a format standard designed to maximise interoperability and functionality. This requires a total application-platofrm-vendor independence that neither ODF or OOXML can claim. The only format that meets these requirements is the W3C's family of HTML-XML formats. These include advancing Compound Docuemnt Framework format components such as (X)HTML-5, CSS-3, XForms, SVG and SMiL.. The W3C's CDF does in fact meet the markeplace needs of a universal format that is open, unencumbered and totally application, platform and vendor independent. The only trick left for CDF is proving that legacy desktop applications can actually implement conversions from existing in-memory-binary-representations to CDF without loss of information.
Gary Edwards

Groklaw - Digging for Truth : The problem with XML document formats - 0 views

www.groklaw.net/comment.php

odf ooxml html webkit groklaw alex-brown document-wars

shared by Gary Edwards on 15 Apr 09 - Cached
  • The problem with that, as I understand it, is that the transitional spec is pretty much unimplementable by anybody except MS
    • Jesper Lund Stocholm
      Jesper Lund Stocholm on 15 Apr 09
       
      Well, herein lies the problem, dude ... you don't understand it.
  • Gary Edwards on 16 Apr 09
     
    Wow! The ODF peasants with pitchforks are have taken to the streets, and ISO document expert Alex Brown is taking them on. The volumes of traffic generated by any discussion of the ISO XML document wars continues to amaze. It's very one sided though. The basic problem seems to be that ISO has accepted two XML document format standards, OOXML and ODF, with OOXML being held to a higher set of expectations than ODF. Alex would do well if he could step back from the OOXML - ODF war, and move the discussion to something like the theoretical IDABC ODEF: the European "Open Document Exchange Formats" design. With ODEF as single set of XML format requirements against which both OOXML and ODF can be measured and compared, Alex might be able to neutralize the heated emotions of angry Open Source - Open Standards - Open Web supporters, who mistakenly think ODF measures up to ODEF expectations and requirements. Trying to compare ODF to OOXML isn't getting us anywhere. At some point, we have to ask ourselves what is it that we want from a standardized XML document format. Having participated in both the Massachusetts pilot study and the California pilot discussions, i have to say that the public expectations were that XML formats would have a basic set of characteristics: open markup; structured separation of content, presentation and logic; high level interoperability (exchange), and Web ready. These are basic "must have" expectations. XML formats were expected to be "better" than 1998 HTML-CSS. But when we apply the basic set of expectations, todays HTML+ (webkit HTML5, CSS4, SVG/Canvas, JS, JS Libs) turns out to be a far better format. Where the XML formats really fall off the wagon are the interoperability and Web ready expectations. For the life of me i don't see how anyone can compare ODF or OOXML interoperability with that of HTML+. And of course, HTML+ is the native language/for
  • Gary Edwards on 16 Apr 09
     
    Jesper Lund Stocholm was kind enough to point out that, once again, GrokLaw is stoking the fires of the XML document wars. This time PJ takes on Alex Brown, of the ISO SC34 document standards group convenor. And Alex responds ... and responds ... and responds. of course, the attacks keep coming! I left Jesper a rather lengthy comment at: http://tinyurl.com/document-wars
Gary Edwards

Dropbox Slashes Its Price as the Cost of a Gigabyte Nears Zero | Business | WIRED - 0 views

www.wired.com/...dropboxs-plan-to-stay-relevant

wordsdk Office-365

shared by Gary Edwards on 28 Aug 14 - No Cached
gravitythread liked it
  • how many gigabytes you can store, and at what price.
  • The cut brings Dropbox in line, once again, with rival services at its gargantuan competitors: Google and Microsoft. But Dropbox’s decision to bury the lead signals something more important about the business it’s in:
  • in the competitive market for file storing, syncing, and sharing, gigabytes don’t matter quite as much as they did in the past.
  • ...8 more annotations...
  • The game is all about what you can do with them.
  • ChenLi Wang, Dropbox’s head of product
  • So, if Dropbox isn’t really selling storage, then what is it selling? Services.
  • The competition becomes squarely about what each competitor can do, rather than how much users can upload.
  • That’s been the approach Microsoft has taken, says Michal Gideoni, director of product management for Office.
  • Gideoni describes storage for Microsoft as just one aspect of its “holistic” approach to the cloud, an approach anchored not by file-syncing but by Office 365, the online version of its iconic productivity software.
  • As at Dropbox, Gideoni talks in terms of workflow, of data on the move, not just of a box for holding data in place.
  • Dropbox for Business also offers deep integration with Office files, but so far those features are not available with the consumer version.
  • Gary Edwards on 28 Aug 14
     
    "When I talk to folks at Dropbox, they're eager to tell me about how different people are using its file-sharing service: the musician, the photographer, the professor, the startup founder. They like to talk about new features, like password-protected links and the remote wipe tool that lets you remove files from a lost computer. But what they save for the end of our meeting, almost like an afterthought, are the two numbers that traditionally meant the most for a data storage service: how many gigabytes you can store, and at what price. As it turns out, these numbers look at lot better than they used to. On Wednesday, the company slashed the price of a gigabyte by 90 percent on Dropbox Pro, the paid version of its signature consumer product. Up until now, users paid $9.99 per month to store up to 100 gigabytes of data. Now, for that same price, they can store one terabyte. The cut brings Dropbox in line, once again, with rival services at its gargantuan competitors: Google and Microsoft. But Dropbox's decision to bury the lead signals something more important about the business it's in: in the competitive market for file storing, syncing, and sharing, gigabytes don't matter quite as much as they did in the past. The game is all about what you can do with them. "It's how you get the content in and out and how does it let you do the work you want to accomplish," says ChenLi Wang, Dropbox's head of product. "We want people to rely on Dropbox as the home for all their stuff as opposed to thinking of it as a fixed storage limit." What Dropbox Is Selling"
Gary Edwards

HTML5 data communications - 1 views

www.networkworld.com/...020911-html5-data.html

visual-document visually-immersive web-document HTML5 Web-Compound-Document

shared by Gary Edwards on 09 Feb 11 - No Cached
    • Gary Edwards
      Gary Edwards on 09 Feb 11
       
      Sounds like the core of a 1992 Windows Desktop Productivity "Compound Document" model.  Applications need to message, exchange and link data.  In 1992, the key technologies embedded in a compound document were DDE, OLE, ODBC, scripts and macros.  Later on, ActiveX and COM was added.  Today the MSOffice desktop productivity environment links into the MS-Live Productivity Cloud or the BPOS - SharePoint private cloud with a raft of WPF-SilverlightX stuff.  Good to see the Open Web fighting back with their own compound document model.
  • Cross-document messaging
Gary Edwards

UseOffice. Net - A Modern Component to Accurately Convert Popular Office Formats - 1 views

www.sbwire.com/...sbwire-104408.htm

cloud-productivity desktop-productivity Document-Management-System

shared by Gary Edwards on 23 Aug 11 - No Cached
  • Gary Edwards on 23 Aug 11
     
    Cloud based Productivity Platforms and Document Management Systems just got a huge "integration with legacy desktop productivity environments"  boot from UseOffice. Net - a powerful component for integration of converting functions to Web-server ASP.NET and desktop applications Windows Forms applications for the platform of Windows, including the following versions: 2000, XP, Vista, 2008 Server, Seven. Applications built on the basis of this component, allow the user to quickly, and most importantly - accurately convert the formats DOC, DOCX, RTF, PPT, PDF, HTML, XHTML various documents - reports, forms, invoices, articles, forms, presentations, web pages etc. The converted documents are fully preserve the visual characteristics of the original, including elements of the structure and format, such as tables, font styles, colors, page margins, etc. UseOffice. Net Supports the following areas of transformation: - DOC to: html, xml, rtf, txt, pdf, docx - DOCX to: html, xml, rtf, txt, pdf, doc - HTML to: doc, rtf, txt, pdf - XLS to: html, xml, txt, csv, rtf, pdf - RTF to: html, xml, txt, doc, pdf - PPT to: html, xml, rtf, pdf, jpg, bmp, gif - XLSX to: html, xml, txt, csv, rtf, pdf Integrate the components into an application quickly and easily - just add a couple lines of code. The component is written in C # and requires the set. NET Framework and Microsoft Office (any version from 2000, XP, 2003, 2007, 2010). The following development environments: C #, VB.Net, J #, C + +. NET, Delphi.NET, ColdFusion 8, ASP.NET, and many others ... Combining ease of use and quality conversion UseOffice. Net allows you to set page numbers in the final document, orientation and page size settings for images and more necessary in the conversion.
Gary Edwards

Microsoft: the cloud as feature - Rough Type - 0 views

www.roughtype.com/...the_web_as_feat.php

microsoft ms-stack msoffice msooxml ooxml

shared by Gary Edwards on 12 Dec 07 - Cached
  • In the short term and even medium term, it is very likely that mainstream business customers will be more comfortable viewing the cloud as an add-on to rather than a replacement for their traditional Office programs. The competitive battle, in other words, will be fought largely on Microsoft's turf, and on that turf a certain amount of messiness is both allowed and expected. "Google and other Office competitors will be breathing a sigh of relief this morning," writes Mike Arrington. If so, it's a sigh they may come to regret.
  • Gary Edwards on 12 Dec 07
     
    Here we go.  The final piece to the MS Stack puzzle falls into place.  Nick Carr provides excellent commentary and analysis.  As usual.
Gary Edwards

What Cloud Means to Marketing Forecast - Nick Carr The Big Switch - 1 views

adage.com/...article

cloud-computing google grid-computing microsoft server-farms

shared by Gary Edwards on 22 Mar 08 - Cached
  • The gorilla in this nascent market is Google. It has been spending billions of dollars to build huge data centers, or "server farms," around the world, enabling it to run all sorts of consumer software and store enormous quantities of personal data. Combine that processing muscle with the company's dominance of web searching and advertising, and you have a juggernaut capable of redefining the software business on the media model.
Gary Edwards

Brian Jones: Open XML Formats : Mapping documents in the binary format (.doc; .xls; .pp... - 0 views

blogs.msdn.com/...pt-to-the-open-xml-format.aspx

burtongroup cdf css ibm iso microsoft odf okelly ooxml opendocument openxml sun w3c xhtml

shared by Gary Edwards on 20 Jan 08 - Cached
  • The second issue we had feedback on was an interest in the mapping from the binary formats into the Open XML formats. The thought here was that the most effective way to help people with this was to create an open source translation project to allow binary documents (.doc; .xls; .ppt) to be translated into Open XML. So we proposed the creation of a new open source project that would map a document written using the legacy binary formats to the Open XML formats. TC45 liked this suggestion, and here was the TC45 response to the national body comments: We believe that Interoperability between applications conforming to DIS 29500 is established at the Office Open XML-to- Office Open XML file construct level only.
    • Gary Edwards
      Gary Edwards on 20 Jan 08
       
      And here i was betting that the blueprints to the secret binaries would be released the weekend before the September 2nd, 2007 ISO vote on OOXML! Looks like Microsoft saved the move for when they really had to use it; jus tweeks before the February ISO Ballot Resolution Meetings set to resolve the Sept 2nd issues. The truth is that years of reverse engineering have depleted the value of keeping the binary blueprints secret. It's true that interoperability with MSOffice in the past was near entirely dependent on understanding the secret binaries. Today however, with the rapid emergence of the Exchange/SharePoint juggernaught, interop with MSOffice is no longer the core issue. Now we have to compete with E/S, and it is the E/S interfaces, protocols and document API's and dependencies tha tmust be reverse engineered. The E/S juggernaught is now surging to 70% or more of the market. These near monopoly levels of market penetration is game changing. One must reverse engineer or license the .NET libraries to crack the interop problem. And this time it's not just MSOffice. Today one must crack into the MS Stack whose core is tha tof MSOffice <> E/S. So why not release the secret binary blueprints? If that's the cost of getting the application, platform and vendor specific OOXML through ISO, then it's a small price to pay for your own international standard.
  • Gary Edwards on 20 Jan 08
     
    Well well well. We knew that IBM had access to the secret binary blueprints back in 2006. Now we know that Sun ALSO had access!
    And why is this important? In June of 2006, Massachusetts CIO Louis Gutierrez asked the OpenDocument Foundation's da Vinci Group to work with IBM on developing the da Vinci ODF plug-in clone of Microsoft's OOXML Compatibility Pack plug-in. When we met with IBM they were insistent that the only way OASIS ODF could establish sufficient compatibility with MSOffice and the billions of binary documents would be to have the secret blueprints open.
    Even after we explained to IBM that da Vinci uses the same internal conversion process that the OOXML plug-in used to convert binaries, IBM continued to insist that opening up the secret binaries was a primary objective of the OASIS ODF community.
    For sure this was important to IBM and Sun, but the secret binaries were of no use to us. da Vinci didn't need them. What da Vinci needed instead was a subset of ODF designed for the conversion of those billions of binary documents! A need opposed by Sun.
    Sun of course would spend the next year developing their own ODF plug-in for MSOffice. But here's the thing: it turns out that Sun had complete access to the secret binary blueprints dating back to 2006!!!!!!
    So even though IBM and Sun have had access to the blueprints since 2006, they have been unable to provide effective conversions to ODF!
    This validates a point the da Vinci group has been trying to make since June of 2006: the problem of perfecting a high fidelity conversion between the billions of binaries and ODF has nothing to do with access to the secret binary blueprints. The real issue is that ODF was NOT designed for the conversion of those binary documents.
    It is true that one could eXtend ODF to achieve the needed compatibility. But one has to be very careful before taking this ro
Gary Edwards

A Graceful Exit for Box? - 0 views

www.cmswire.com/...aceful-exit-for-box-026225.php

wordsdk Office-365 Cloud-Productivity-Platform

shared by Gary Edwards on 20 Aug 14 - No Cached
  • Gary Edwards on 20 Aug 14
     
    "What's less likely to be out for display are Box's miserable finances, its delayed IPO and talk of increasing competition from industry giants like Microsoft, EMC, Google, Citrix, VMWare, Amazon and fellow Sync and Share startup Dropbox. Though you certainly don't see Levie sweating in public, he has to be feeling the heat. Consider that one year ago analyst Forrester gave Box the pole position in the Enterprise File Sync and Share (EFSS) space, by last month Gartner tagged it as the third of four leaders in its Magic Quadrant for EFSS."
‹ Previous 21 - 34 of 34
Showing 20▼ items per page