Skip to main content

Home/ Open Web/ Group items matching "HTML5-Native-Client" in title, tags, annotations or url

Group items matching
in title, tags, annotations or url

Sort By: Relevance | Date Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

Ex-Apple Javascript Guru: HTML5 and Native Apps Can Live Together: Tech News « - 0 views

  •  
    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.
Gary Edwards

Google shows Native Client built into HTML 5 | Webware - CNET- Shankland - 0 views

  •  
    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.
Gary Edwards

Adobe to Jobs: 'What the Flash do you know?' * The Register - 0 views

  •  
    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."
Gary Edwards

Apple, Microsoft Challenged By Streaming Software Plan - Cloud - 0 views

  •  
    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."
Gary Edwards

Google shows Native Client built into HTML 5 - ZDNet.co.uk - 0 views

  •  
    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.
Gary Edwards

Microsoft Office fends off open source OpenOffice and LibreOffice but cloud tools gain ground | ZDNet - 0 views

  •  
    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.
Gary Edwards

Is the Apps Marketplace just playing catchup to Microsoft? | Googling Google | ZDNet.com - 0 views

shared by Gary Edwards on 12 Mar 10 - Cached
  • Take the basic communication, calendaring, and documentation enabled for free by Apps Standard Edition, add a few slick applications from the Marketplace and the sky was the limit. Or at least the clouds were.
    • Gary Edwards
       
      Google Apps have all the basic elements of a productivity environment, but lack the internal application messaging, data connectivity and exchange that made the Windows desktop productivity platform so powerful.   gAPPS are great.  They even have copy/paste! But they lack the basics needed for simple "merge" of client and contact data into a wordprocessor letter/report/form/research paper. Things like DDE, OLE, ODBC, MAPI, COM, and DCOM have to be reinvented for the Open Web.   gAPPS is a good place to start.  But the focus has got to shift to Wave technologies like OT, XMPP and JSON.  Then there are the lower level innovations such as Web Sockets, Native Client, HTML5, and the Cairo-Skia graphics layer (thanks Florian).
  • Whether you (or your business) choose a Microsoft-centered solution that now has well-implemented cloud integration and tightly coupled productivity and collaboration software (think Office Live Web Apps, Office 2010, and Sharepoint 2010) or you build a business around the web-based collaboration inherent in Google Apps and extend its core functions with cool and useful applications, you win.
    • Gary Edwards
       
      Not true!!! The Microsoft Cloud is based on proprietary technologies, with the Silverlight-OOXML runtime/plug-in at the core of a WPF-.NET driven "Business Productivity Platform. The Google Cloud is based on the Open Web, and not the "Open Web" that's tied up in corporate "standards" consortia like the W3C, OASIS and Ecma. One of the reasons i really like WebKit is that they push HTML5 technologies to the edge, submitting new enhancements back into the knuckle dragging W3C HTML5 workgroups as "proposals".  They don't however wait for the entangled corporate politics of the W3C to "approve and include" these proposals.  Google and Apple submit and go live simultaneously.   This of course negates the heavy influence platform rivals like Microsoft have over the activities of corporate standards orgs.  Which has to be done if WebKit-HTML5-JavaScript-XMPP-OT-Web Sockets-Native Client family of technologies is ever to challenge the interactive and graphical richness of proprietary Microsoft technologies (Silverlight, OOXML, DrawingML, C#). The important hedge here is that Google is Open Sourcing their enhancements and innovations.  Without that Open Sourcing, i think there would be reasons to fear any platform player pushing beyond the corporate standards consortia approval process.  For me, OSS balances out the incredible influence of Google, and the ownership they have over core Open Web productivity application components. Which is to say; i don't want to find myself tomorrow in the same position with a Google Open Web Productivity Platform, that i found myself in with the 1994 Windows desktop productivity environment - where Microsoft owned every opportunity, and could take the marketshare of any Windows developed application with simple announcements that they to will enter that application category.  (ex. the entire independent contact/project management category was wiped out by mere announcement of MS Outlook).
Gary Edwards

Google talks Chrome OS, HTML5, and the future of software - 1 views

  •  
    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
Gary Edwards

I, Cringely » Blog Archive » iCloud's real purpose: kill Windows - Cringely on technology - 0 views

  •  
    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.
1 - 9 of 9
Showing 20 items per page