Gary Edwards's Library tagged webkit_chromium →  View Popular

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.

news.cnet.com/8301-17939_109-10251563-2.html - Preview

Google-Native-Client HTML5 GWT Wave Web-Worker-Threads webkit_chromium Chrome O3D

<i>"........ 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.

However, Google wants to make the technology more broadly accessible in browsers through new technology coming to HTML, the standard used to build Web pages, and at the Google I/O developer conference Thursday demonstrated its work to make that happen...."</i>

Looks to me that Google is attacking the problem of integrating a Chrome browser with x86 desktop metal. Maybe it's the only way to get webkit/Chromium Web Apps on a par with native x86-Windows desktop apps?

There is that infamous quote describing the Google v Microsoft challengeto consider: "Google has to replace the MSOffice productivity environment on the desktop "Client" before Microsoft replaces Google apps and services on the "Server". (Same holds true for IBM Lotus Notes - WebSphere on the Server and OpenOffice/Symphony on the desktop client).

The quote actually comes from some high level Microsoft document experts, said to have been uttered while under the glaze of legendary Czech Pilsners during a recent ISO meet up in Prague. Looks like there is far more to this quote than meets the eye. I wonder though. Google is looking good. So good that perhaps they are confident enough to take things public - as the events at Google I/O seem to indicate?

~ge~

news.cnet.com/8301-17939_109-10251563-2.html - Preview

html5 html+ webkit webkit_chromium x86-Chrome

Recently the Rocketman and i have been arguing about webkit/Chromium DOM capabilities and limitations; like the failure to fully implement CSS3! Especially missing is support for CSS3 page layout / page break innovations. I realized that i didn't have a good understanding of browser DOM - client side issues, and came across this interesting post from Dave Ward concerning DOM and jQuery. <br>\nThe core issue behind my discussions with the Rocketman have to do with creating a DOM view from OpenXML and ODF documents, and then passing that view to the webkit/Chromium engine. So we weren't all that interested in cross browser support or in how IE8 handles DOM-JavaScript. Dave Ward however not only provides a good discussion about DOM-JavaScript and the importance of jQuery as a force of interoperability, he also points out that Microsoft supports jQuery - including direct support within Visual Studio!<br>\n\n<i>".....Though JavaScript itself is a great programming language, the document object model (DOM) can be a web developer's worst nightmare.  The DOM is a method through which browsers expose an interface allowing JavaScript code to manipulate elements, handle events, and perform other tasks related to a document within the browser.  While almost every browser implements an ECMA standard version of JavaScript, their DOM implementations are inconsistent and quirky at best.  In fact, if you've had bad experiences with client-side programming in the past, it's likely that the DOM was the true source of your frustrations, not JavaScript itself.  This is exactly the pain point which jQuery addresses....</i><br>\n\n<i>..... "Officially supported by Microsoft - For many Microsoft developers, this official blessing is the clincher. Not only will Microsoft begin including jQuery with Visual Studio, but it is part of the default ASP.NET MVC project template. What's more, Microsoft Product Support Services has already begun offering support for jQuery."....</i>\n\njQuery abstracts the DOM away, allowing you to focus o

visitmix.com/...opers-Should-Know-About-jQuery - Preview

jQuery DOM ASP.NET JavaScript webkit_Chromium Platinum Glimmer