Group items tagged

Quick review of different sync-share-store services, starting with DropBox and ending with three Open Source services. Very interesting. Things have progressed since I last worked on the SurDocs project for Sursen. No mention in this review of file formats, conversion or viewing issues. I do know that CrocoDoc is used by near every sync-share-store service to convert documents to either pdf or html formats for viewing. No servie however has been able to hit the "native document" sweet spot. Not even SurDocs - which was the whole purpose behind the project!!! "Native Documents" means that the document is in it's native / original application format. That format is needed for the round tripping and reloading of the document. Although most sync-share-store services work with MSOffice OXML formatted documents, only Microsoft provides a true "native" format viewer (Office 365). Office 365 enables direct edit, view and collaboration on native documents. Which is an enormous advantage given that conversion of any sort is guaranteed to "break" a native document and disrupt any related business processes or round tripping need. It was here that SurDoc was to provide a break-through technology. Sadly, we're still waiting :( excerpt: The availability of cheap, easy-to-use and accessible cloud file-sharing services means users have more freedom and choice than ever before. Dropbox pioneered simplicity and ease of use, and so quickly picked up users inside the enterprise. Similar services have followed Dropbox's lead and now there are dozens, including well-known ones such as Google Drive, SkyDrive and Ubuntu One. cloud.jpg Valdis Filks , research director at analyst firm Gartner explained the appeal of cloud file-sharing services. Filks said: "Enterprise employees use Dropbox and Google because they are consumer products that are simple to use, can be purchased without officially requesting new infrastructure or budget expenditure, and can be installed qu

Odd that the reporter mentions the importance of security near the top of the article but gives that topic such short shrift in his evaluation of the services. For example, "secured by 256-bit AES encryption" is meaningless without discussing other factors such as: [i] who creates the encryption keys and on which side of the server/client divide; and [ii] the service's ability to decrypt the customer's content. Encrypt/decryt must be done on the client side using unique keys that are unknown to the service, else security is broken and if the service does business in the U.S. or any of its territories or possessions, it is subject to gagged orders to turn over the decrypted customer information. My wisdom so far is to avoid file sync services to the extent you can, boycott U.S. services until the spy agencies are encaged, and reward services that provide good security from nations with more respect for digital privacy, to give U.S.-based services an incentive to lobby *effectively* on behalf of their customer's privacy in Congress. The proof that they are not doing so is the complete absence of bills in Congress that would deal effectively with the abuse by U.S. spy agencies. From that standpoint, the Switzerland-based http://wuala.com/ file sync service is looking pretty good so far. I'm using it.

Whoops. This is the better article! ZDNet got the dregs. CNET got the real thing: Google Native Client, HTML5, GWT, Wave, Web Worker Threads, webkit/chromium, Chrome, O3D "Google wants its Native Client technology to be a little more native. Google Native Client, still highly experimental, lets browsers run program modules natively on an x86 processor for higher performance than with Web programming technologies such as JavaScript or Flash that involve more software layers to process and execute the code. But to use it, there's a significant barrier: people must install a browser plug-in.

Google has released a programming tool to help move its Native Client project--and more broadly, its cloud-computing ambitions--from abstract idea to practical reality. The new Native Client software developer kit, though only a developer preview version, is designed to make it easier for programmers to use the Net giant's browser-boosting Native Client technology. "The Native Client SDK preview...includes just the basics you need to get started writing an app in minutes," Google programmer David Springer said Wednesday in a blog post announcing the SDK, a week before the developer-oriented Google I/O conference. "We'll be updating the SDK rapidly in the next few months."

Good interview with Charles Jolley - SproutCore - WebKit (met Charles at Web 2.0).  He has left Apple and started a SproutCore Web App development company called "Strobe".  Looking very good Charles! The Blended Brew Apps have become a preferred way of accessing information on mobile devices. But developers want to provide a unified experience, and that is why Jolley believes that we will soon have apps that use HTML5 inside a native app wrapper. "People are looking for an either/or solution, but it is not going to end up like that," he said. Think of Strobe's offerings as a way to create an experience that is a blend of HTML5 and native mobile apps. How this works is that an application is developed in HTML5 instead of proprietary formats. It is wrapped in a native app wrapper for, say, the iPhone, but when accessed through a web browser on a PC or any other device, like tablet, it offers the same user experience. This is a good way to solve a problem that is only going to get compounded many fold as multiple endpoints for content start to emerge. The co-existence of web and native apps also means content publishers need to think differently about content and how it is offered to consumers. The multiplicity of endpoints (iPhone, iPad, TV and PC) is going to force content producers to think differently about how they build the user experiences for different sets of screens. Jolley argues that the best way to do so is to stop taking a document-centric view that is part of the PC-era. In the touch-based mobile device era, folks need to think of ways to have a single technology stack married to the ability to create unique experiences for different devices. And if you do that, there is no doubt that HTML5 and native apps can live in harmony.

Very interesting the way JavaScript Libraries are continuing to challenge Native Code for Web Application dominance.    excerpt: "The code library, ORBX.js, can be thought of as a cloud-based alternative to Google's Native Client technology. It permits Linux, OS X and Windows applications to run on remote servers and to be presented in a Web browser." "With ORBX.js, native code and legacy applications can be hosted in the cloud (e.g. Amazon EC2), and stream interactive graphics, 3D rendering or low latency video to a standard HTML5 page without using plugins or native code, or even the video tag (which, like Google NaCL,is vendor specific - ORBX.js works on all five major browsers)," explained Otoy founder and CEO Jules Urbach in an email. "The video codec created for ORBX.js can decode 1080p60 at a quality on par with H.264, using only JavaScript." "With ORBX.js and a cloud service provider, you could conceivably run Value's PC Steam client on an Apple iMac or Google Chromebook. You could run Autodesk 3DS Max 2014 on an Android Nexus 7 tablet. You could run a big budget, graphically demanding game title like Left 4 Dead 2 in a Web browser, without any plugins, Flash, Java, NaCL or other supporting technology."

Good article from Stephen Shankland describing how the Wave-HTML5-O3D-Web Worker pieces fit. He left out GWT. But this after all, one very big picture. Google has thrown down a game changer. Wave represents one of those rare inflection points where everything immediately changes. There is no way to ignore the elephant that just sat on your face. Google has been demonstrating its sandboxing technology for making web applications perform at similar levels to those associated with native desktop applications. Google Native Client, still highly experimental, lets browsers run program modules natively on an x86 processor for higher performance than with web-programming technologies, such as JavaScript or Flash, that involve more software layers to process and execute the code. But to use it, there is a significant barrier: people must install a browser plug-in.

Comment posted 1 week ago in reply to Zzgomes .....  by Ed Carp.  Finally someone who gets it! OBTW, i replaced Windows 7 with Linux Mint over a year ago and hope to never return.  The thing is though, i am not a member of a Windows productivity workgroup, nor do i need to connect to any Windows databases or servers.  Essentially i am not using any Windows business process or systems.  It's all Internet!!! 100% Web and Cloud Services systems.  And that's why i can dump Windows without a blink! While working for Sursen Corp, it was a very different story.  I had to have Windows XP and Windows 7, plus MSOffice 2003-2007, plus Internet Explorer with access to SharePoint, Skydrive/Live.com.  It's all about the business processes and systems you're part of, or must join.   And that's exactly why the Linux Desktop has failed.  Give Cloud Computing the time needed to re-engineer and re-invent those many Windows business processes, and the Linux Desktop might suceed.  The trick will be in advancing both the Linux Desktop and Application developer layers to target the same Cloud Computing services mobility targets.  ..... Windows will take of itself.   The real fight is in the great transition of business systems and processes moving from the Windows desktp/workgroup productivity model to the Cloud.  Linux Communities must fight to win the great transition. And yes, in the end this all about a massive platform shift.  The fourth wave of computing began with the Internet, and will finally close out the desktop client/server computing model as the Web evolves into the Cloud. excerpt: Most posters here have it completely wrong...the *real* reason Linux doesn't have a decent penetration into the desktop market is quite obvious if you look at the most successful desktop in history - Windows.  All this nonsense about binary driver compatibility, distro fragmentation, CORBA, and all the other red herrings that people are talking about are completely irrelevant

Good quotes.  The Wired article is also worth reading.  The important take away being that Apple is fully committed to native browser HTML5.  So is Google.  But, i found out at the Web 2.0 - WebKit party in 2009, there is quite a bit of tension between Apple WebKit and Google.  The problem being that Apple is doing all the work while Google is pumping up HTML5, Web Sockets and Native Client; all of which are essential to WebKit, but also to Chrome OS, Chrome, Android and the Google Apps push. excerpt:  According to Wired, at an Apple "town hall" meeting after the introduction of the Flashless iPad, Steve Jobs unloaded on Google, calling the search giant's "don't be evil" motto "bullshit," before rounding on Adobe. "They are lazy. They have all this potential to do interesting things, but they just refuse to do it," he said. "Apple does not support Flash because it is so buggy... Whenever a Mac crashes more often than not it's because of Flash. No one will be using Flash...The world is moving to HTML5."

Interesting stats coming out from the recent Forrester study on Office Productivity.  The study was conducted by Philipp Karcher, and it shows a fcoming collision of two interesting phenomenon that cannot continue to "coexist".  Something has to give. The two phenom are the continuing dominance and use of client/server desktop productivity application anchor, MSOffice, and, the continuing push of all business productivity application to highly mobile cloud-computing platforms.   It seems we are stuck in this truly odd dichotomy where the desktop MSOffice compound document model continues to dominate business productivity processes, yet those same users are spending ever more time mobile and in the cloud.  Something has got to give. And yes, I am very concerned about the fact that neither of the native XML document formats {used by MSOffice (OXML), OpenOffice and LibreOffice (ODF)} are designed for highly mobile cloud-computing.   It's been said before, the Web is the future of computing.  And HTML5 is the language of the Web.  HTML is also the most prolific compound-document format ever.  One of the key problems for cloud-computing is the lack of HTML5 ready Office Productivity Suites that can also manage the complexities of integrating cloud-ready data streams. Sadly, when Office Productivity formats went down the rat hole of a 1995 client/server compound document model, the productivity suites went right with them.  Very sad.  But the gaping hole in cloud-computing is going to be filled.  One way or the other.

Interesting article describing a recent press conference where Microsoft introduced their latest SkyDrive alternative to Apple's iCloud initiative.  Having had considerable experience with SkyDrive and the entire "sync-share-store" Cloud category, I left a lengthy comment. Computerworld - Microsoft is pitching its SkyDrive online storage service to Office for Mac users, calling Apple's iCloud offering "not enough" for collaboration, file sharing and anywhere-access to documents. Microsoft released an OS X SkyDrive client preview two weeks ago, adding Macs to the list of devices -- Windows, particularly the upcoming Windows 8, iOS and Windows Phone -- with native support for the Dropbox-like service. On Monday, the Redmond, Wash. developer stumped for SkyDrive on its Office for Mac website. "With the SkyDrive for Mac OS X Lion preview, SkyDrive for Windows, and the release of SkyDrive for iPad, you can save and store your important documents or other files in the SkyDrive folder in Finder and access them from anywhere," the Office for Mac team wrote on its blog.

Matthew Papakipos, the engineering director for the Chrome OS project, and Eitan Bencuya, from Google PR. Over the course of the interview, Papakipos and Bencuya go into considerable detail about topics that range from big-picture perspectives on how Google develops software and where it sees the Web going with HTML5, to the nuts and bolts of what Chrome OS is slated to offer in specific areas. In short, we cover the following ground: ... How and when the Chrome OS project was conceived... The relationship between Chrome OS and Android... How Google is trying to tackle the same "file handler" problem as Windows OLE and the registry, but in the cloud.... Who Google sees as the target audience for Chrome OS, how did they decide which projects and features to pursue... The convergence of the phone and the computer... Nuts and bolts details, like native client execution, security, and UI issues... The significance of Chrome's built-in media player

First, what is a "cloud OS" and why should I want one? Actually, I don't even know if anyone calls it a "cloud OS", but I couldn't find a better generic term for something like ChromeOS. The basic idea is that apps and data all live on the Internet, which is has been renamed "The Cloud" since that sounds cooler, and your laptop or whatever is basically just a window into that cloud. If your laptop is stolen or catches fire or something, it's not a big deal, because you can just buy another one and nothing has been lost (except your money). Many people characterize this approach as using a "dumb terminal", but that's wrong. Your local computer can still do all kinds of smart computation and data manipulation -- it's just no longer the single point of failure. To me, the defining characteristic of cloud based apps is "information without location". For example, in the bad old days, you would install a copy Outlook or other email software on your PC, it would download all of your email to your computer, and then the email would live on that computer until Outlook corrupted its PST file and everything was lost. If you accidentally left your computer at home, or it was stolen, then you simply couldn't get to your email. Information behaved much like a physical object -- it was always in one place. That's an unnecessary and annoying limitation. By moving my email into "the cloud", I can escape the limitations of physical location and am able to reach it from any number of computers, phones, televisions, or whatever else connects to the Internet. For performance and coverage reasons, those devices will usually cache some of my email, but the canonical version always lives online. The Gmail client on Android phones provides a great example of this. It stores copies of recent messages so that I can access them even when there is no Internet access, and also saves any recent changes (such as new messages or changes to read state), but as soon as possible it sends those chang

I'm not convinced that iCloud will eliminate Windows, MAC and Linux desktops.  I've been using DropBox, SyncDocs, Live.com while testing a number of backup-store-synch-share file services. IMHO, it's all about the apps that act on your data.  And these can come from the desktop, the Browser, or the device.  The best app platform for Cloud hosted data seems to be moving towards HTML5-JS.  Not Win32, .NET, C#, Java or Cocoa (iOS).  And Google clearly has he best platform of integrated services and API's.  They are best positioned to win the Cloud Wars if HTM5-JS and Native Client can close the deal on Cloud apps.  IMHO. excerpt: Apple's announcements yesterday about OS X 10.7 pricing (cheap), upgrading (easy), iOS 5, and iCloud storage, syncing, and media service can all be viewed as increasing ease of use, but from the perspective of Apple CEO Steve Jobs they perform an even more vital function - killing Microsoft. Here is the money line from Jobs yesterday: "We're going to demote the PC and the Mac to just be a device - just like an iPad, an iPhone or an iPod Touch. We're going to move the hub of your digital life to the cloud." Just like they used to say at Sun Microsystems, the network is the computer. Or we could go even further and say our data is the computer. This redefines digital incumbency. The incumbent platform today is Windows because it is in Windows machines that nearly all of our data and our ability to use that data have been trapped. But the Apple announcement changes all that. Suddenly the competition isn't about platforms at all, but about data, with that data being crunched on a variety of platforms through the use of cheap downloaded apps.

A Complete Document Management System packaged as a server appliance.  Still needs wiki-WORD sync-share-collaborate.  Still needs portable "native client" docx viewer/editor with fixed/flow/flock options. Good solution for SMB:  instead of trusting business documents to a Cloud provider, they can purchase the Treeno DMS-Cloud appliance and do it themselves. Treeno Document Vault 2.0 - document management appliance. The new Treeno Document Vault is designed specifically for the small to medium sized business. It is a completely self-contained plug-and-play document management server appliance. Treeno's EDM solutions include document, imaging, email and document workflow management. Treeno Software's mission is to provide their customers with operational workflow efficiencies and measureable return on investment (ROI) through the fast installation and implementation of their fully secure, highly reliable, and easy-to-use, web-based Enterprise Document Management (EDM) Solution. For more information on Treeno Software, please visit www.treenosoftware.com