Gary Edwards's Library tagged Google →  View Popular

Great stats and charts!  Here comes the Android.

excerpt: Google's Android operating system has plenty to celebrate this holiday season -- and now, a new trio of studies suggests the platform is poised for even more success in 2010.

There's no question Android's been enjoying plenty of time in the spotlight since the launch of Motorola's Droid smartphone. But with dozens of new Android devices expected to debut in the coming months -- possibly even including the omnipotent "Google Phone" (have you seen the things that phone can do?) -- the biggest burst may still be ahead.

www.pcworld.com/...asion_prepare_for_phase_2.html - Preview

Open-Web Android iphone Google

Google tests a service called Cloudboard, an online clipboard that should make it easy to copy data between Gmail, Google Docs and other Google services. The service is not publicly available yet, but there are many references to it.

lengthy comment from ~ge~

googlesystem.blogspot.com/...google-cloudboard.html - Preview

ge Open-Web MS-WebStack Google unified-productivity

Interesting discussion about SVG, and the push Google is making with their SVG Conference.

excerpt:  Vector graphics describe imagery mathematically with lines, curves, shapes, and color values rather than the grid of colored pixels used by bitmapped file formats such as JPEG or GIF widely used on the Web today. Where appropriate, such as with corporate logos but not photographs, vector graphics bring smaller file sizes and better resizing flexibility. That's good for faster downloads and use on varying screen sizes.

news.cnet.com/8301-30685_3-10365636-264.html - Preview

SVG Google Flash Air Silverlight

Excellent Wave coverage from Scott M. Fulton III.  The Hollywood Movie industry use case scenario is very interesting.  But Scott is one of the few people to draw an analogy between Google Wave convergence of concurrent communications and collaborative content and the early days of the Microsoft Office Productivity Platform where we saw DDE, OLE and MAPI rise and rule.

Excerpt: Today, Google is expected to invite as many as 100,000 more participants into the private beta of its concurrent communications system, called Wave. As that happens, many more participants will be able to not only communicate with one another in a more granular form of real-time, but potentially collaborate on work and projects.
It's that latter part of the program that's supposed to congeal at some point into a collective sense of purpose. But this time, unlike Microsoft's first experiments with Dynamic Data Exchange between applications on the same computer three decades ago, there isn't yet a clear, single purpose for the system. No question it could bring individuals as close together as people separated by indefinite distance could become; but as to the question of what they do with one another once they do get together, Google is hoping this question -- like so many others it puts out there in the open -- resolves itself.

Yesterday, Google offered links to a number of different independent assessments of the possible, eventual purpose of Google Wave, though it offered them as use-case scenarios rather than projections of possible goals for the product...which is what many actually were.

www.betanews.com/...1254330877 - Preview

Wave Google

Michael Hickins weighs in the war between Microsoft and Google.  This time he focuses in Microsoft's attempt to move the point of assembly from the desktop productivity environment to an exclusive MS-Web center.

The question is whether enterprises will move to Google (or some other standards- and Web-based vendor) in time, or whether they will get trapped in the fly-paper of Microsoft code, from which they will be hard pressed to detach their documents. This was the problem Massachusetts faced when the state wanted to abandon Microsoft in favor of standards-based applications; their legacy documents were filled with Microsoft code they couldn’t translate cleanly into another format.

When the race is finished, that may turn out to be Microsoft’s greatest strength. While the rest of the world embraces openness and cooperation, Microsoft remains proprietary and closed like a fist.

industry.bnet.com/...t-and-googles-online-collision - Preview

Microsoft Google Point-of-Assembly productivity-environment

The more things change, the more they remain the same.

Excerpt: Microsoft's chief Washington lobbyist has been convening regular meetings attended by the company's outside consultants that have become known by some beltway insiders as "screw Google" meetings, DailyFinance has learned.

The meetings are part of an ongoing campaign by Microsoft (MSFT), other Google (GOOG) opponents, and hired third parties to discredit the Web search leader, according to multiple sources with knowledge of the matter.

"Microsoft is at the center of a group of companies who see Google as a threat to them in some combination of business and policy," said a source familiar with the matter, who requested anonymity to avoid retribution. "The effort is designed make Google look like the big high-tech bad guy here."

Microsoft lobbyist, the Law Media Group, has several people who work full-time on Google-bashing. Everybody knows Microsoft is trying to throw roadblocks at Google and knock them off their game. Microsoft is trying to harm Google in the regulatory, legal, and litigation arenas because they're having problems with Google in the competitive marketplace."
"This is textbook Microsoft," the source adds. "Microsoft has got some of the best, highest-priced lobbyists that money can buy in Washington."

www.dailyfinance.com/...t-screw-google-meetings-in-d-c - Preview

microsoft google anti-trust

This is a really good descriptive "story" about Google Wave, and why it' revolutionary.

www.suntimes.com/...tko-google-wave-060309.article - Preview

wave google wave-maker

Om Malik has an interesting commentary on Google Voice, the Android OS, and a new gVoice application for iPhones and Androids. For sure, new gVoice app meshes into the Andorid OS as if it were hard coded into the silicon.

I left a lengthy comment in the discussion section describing my experiences with gVoice and what i see emerging as Google's Unified Productivity Platform. Of course, gWave, Chrome, Chrome OS, webkit-HTML+, and the sweep of Google Web applications and service come into play.

Excerpt: Can Google be your phone company? The answer is yes. I came to that conclusion after I met with Vincent Paquet, co-founder of GrandCentral (a company acquired by Google) and now a member of the Google Voice team. Earlier today he stopped by our office to show the mobile app versions of its Google Voice service for Blackberry and Android. Google recently announced that it was going to make the Voice service widely available to users in the U.S. soon.

gigaom.com/...meet-google-your-phone-company - Preview

wave unified-productivity google android chrome chromeOS webkit

Some good commentary on chrome OS from InformationWeek's Thomas Claburn.

Excerpt: With Chrome OS, Google aims to make the Web the primary platform for software development.......

The fact that Chrome OS applications will be written using open Web standards like JavaScript, HTML, and CSS might seem like a liability because Web applications still aren't as capable as applications written for specific devices and operating systems.

But Google is betting that will change and is working to effect the change on which its bet depends. Within a year or two, Web browsers will gain access to peripherals, through an infrastructure layer above the level of device drivers. Google's work with standards bodies is making that happen.....

..... According to Matt Womer, the "ubiquitous Web activity lead" for W3C, the Web standards consortium, Web protocol groups are working to codify ways to access peripherals like digital cameras, the messaging stack, calendar data, and contact data.

There's now a JavaScript API that Web developers can use to get GPS information from mobile phones using the phone's browser, he points out. What that means is that device drivers for Chrome OS will emerge as HTML 5 and related standards mature. Without these, consumers would never use Chrome OS because devices like digital cameras wouldn't be able to transfer data.

Womer said the standardization work could move quite quickly, but won't be done until there's an actual implementation. That would be Chrome OS......

..... Chrome OS will sell itself to developers because, as Google puts it, writing applications for the Web gives "developers the largest user base of any platform."

www.informationweek.com/...showArticle.jhtml - Preview

chromeOS OpenWeb Google HTML+ W3C

.... "While i don't see Google or anyone else replacing the MSOffice productivity environment anytime soon, i do see Google challenging Microsoft wherever the Web comes into play. As for the future, that battle for desktop productivity will take place, just not with ChromeOS, Linux, or, the MacOS. What has to happen before the assault on the Microsoft's productivity empire can begin is that the business systems bound to the MSOffice productivity environment must transition to the Open Web, via SaaS or some other replacement. Or, the productivity environment itself must be re-purposed to the Open Web.

The tricky part will be that re-purposing play. ChromeOS is a blockbuster announcement. Not a declaration of war, but a shot across the bow that shouts; Google will defend the Open Web, and profitable business they have there. .....

~ge~

www.businessinsider.com/oblem-wheres-the-market-2009-7 - Preview

ge chromeOS google google-wave

Introducing the Chrome OS alternative to Windows:

excerpt: What Google is doing is not recreating a new kind of OS, they’re creating the best way to not need one at all.

So why release this new OS instead of using Android? After all, it has already been successfully ported to netbooks. Google admits that there is some overlap there. But a key difference they don’t mention is the ability to run on the x86 architecture. Android cannot do that (though there are ports), Chrome OS can and will. But more, Google wants to emphasize that Chrome OS is all about the web, whereas Android is about a lot of different things. Including apps that are not standard browser-based web apps.

But Chrome OS will be all about the web apps. And no doubt HTML 5 is going to be a huge part of all of this. A lot of people are still wary about running web apps for when their computer isn’t connected to the web. But HTML 5 has the potential to change that, as you’ll be able to work in the browser even when not connected, and upload when you are again.

www.techcrunch.com/...crosoft-and-its-made-of-chrome - Preview

chrome google windows

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. \n\nGoogle has been demonstrating its sandboxing technology for making web applications perform at similar levels to those associated with native desktop applications.\n\nGoogle 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.

news.zdnet.co.uk/...0,1000000097,39657632,00.htm - Preview

wave html5 html+ gwt O3D web-workers google

What a loaded statement. This was at the beginning of Google I/O. Incredibly, the rest of the show proved their point. Google backed up all the grand assertions with running code and developer affirmations. Incredible. Here's a taste:

<i>...Google, Mozilla, and Palm gave us all a big whack upside the head this morning. As Shakespeare said, "The hot blood leaps over the cold decree." The technology is here even if the standards committees haven't caught up. Developers are taking notice of these new features, and aren't waiting for formal approval. That's as it should be. As Dave Clark described the philosophy of the IETF with regard to internet standardization, "We reject: kings, presidents, and voting. We believe in: rough consensus and running code."
<br>
Support by four major browsers adds up to "rough consensus" in my book. We're seeing running code at Google I/O, and I'd imagine the 4000 developers in attendance will soon be producing a lot more. So I think we're off to the races. As Vic said to me in an interview yesterday morning, "The web has not seen this level of transformation, this level of acceleration, in the past ten years."</i>

radar.oreilly.com/...google-bets-big-on-html-5.html - Preview

webkit web-3.0 webkit-chromium google html5 css4

Surprise—to make more money!
After the initial burst of discussion about Google putting their toe into the standardized metadata water, I started wondering about the corner of the pool they had chosen. They're not ready to start parsing any old RDFa; they'll be looking for RDFa that uses the vocabulary they somewhat hastily defined for the purpose. Why does the vocabulary define the properties that it defines?

It will be interesting to see how the big hustling SEO world adapts to this. In the words of Drupal project lead Dries Buytaert, Structured data is the new search engine optimization. When he writes "Every webmaster wanting to improve click-through rates, reduce bounce rates, and improve conversation rates, can no longer ignore RDFa or Microformats", it reminds me that when the SEO world eventually gravitates more in the RDFa direction or the microformats direction, these very quantitative, results-driven people will have some real data to explain why. I'll have to start searching their voluminous discussions out there to see what people are saying.

www.snee.com/...gle-and-rdfa-what-and-why.html - Preview

RDFa metadata bobdc google

Google "Rich Snippets" is a new presentation of HTML snippets that applies Google's algorithms to highlight structured data embedded in web pages.

Rich Snippets give end-users convenient summary information about their search results at a glance. Google is currently supporting a very limited subset of data about <b>reviews and people</b>. When searching for a product or service, users can easily see reviews and ratings, and when searching for a person, they'll get help distinguishing between people with the same name. It's a simple change to the display of search results, yet our experiments have shown that users find the new data valuable.

For this to work though, both Web-masters and Web-workers have to annotate thier pages with structured data in a standard format. Google snippets supports microformats and RDFa. Existing Web data can be wrapped with some additional tags to accomplish this.

Notice that Google avoids mention of RDF and the W3C's vision of a "Semantic Web" where Web objects are fully described in machine readable semantics. Over at the WHATWG group, where work on HTML5 continues, Google's Ian Hickson has been fighting RDFa and the Semantic Web in what looks to be an effort to protect the infamous Google algorithms.

RDFa provides a means for Web-workers, knowledge-workers, line-of-business managers and document generating end-users to enrich their HTML+ with machine semantics. The idea being that the document experts creating Web content can best describe to search engine and content management machines the objects-of-information used. The google algorithms provide a proprietary semantics of this same content.

The best solution to the tsunami of conten the Web has wrought would be to combine end-user semantic expertise with Google algorithms. Let's hope Google stays the RDFa course and comes around to recognize the full potential of organizing the world's information with the input of content providers.

One thing the world desperately needs are powerful desktop editors capable of

googlewebmastercentral.blogspot.com/...introducing-rich-snippets.html - Preview

rdfa rich-snippets google html5 odf ooxml w3c

I think the situation for Microsoft is far worse than this article suggests.

The Web is moving into the center of everything. Legacy client/server systems are gradually transitioning to a client/ WebStack-Cloud-RiA /server model. Business processes are either enhanced with Web collaboration, connectivity and exchange, or, re-engineered entirely to become Web centric.

With their Windows and MSOffice productivity environment monopoly, Microsoft pretty much owns the "client" in client/server. Control over the API gave then considerable competitive advantages that rather quickly put them in position to seize profitable opportunities at will. The question has been; can Microsoft control the great transition of legacy desktop bound client/server systems to the Web? Can they leverage the desktop monopoly into a Web monopoly?

www.businessinsider.com/dows-mobile-biting-dust-2009-4 - Preview

webkit google android

The race is on. Google will win the consumer Web. Microsoft will win the business Web.

Sadly i don't think there is any way for Google to challenge Microsoft with regard for the privilege of transitioning existing MSOffice bound workgroup- workflow business processes to the Web. Even if Google Docs could match MSOffice feature to feature, cracking into existing MSOffice workgroups is impossibly hard. Anyone who doubts this ought to take a second look at the Massachusetts ODF Pilot Study, or the recently released Belgium Pilot results. Replacing MSOffice in a workgroup setting is simply too disruptive and costly because of the shared business process problem.

talkback.zdnet.com/5208-11470-0.html - Preview

ge webkit zdnet MSOffice Google-Docs Google Microsoft

Response to the InformationWeek article "Remaking Microsoft: Get Out of Web Search!". Covers "The Myth of Google Enterprise Search", and the refusal of Google to implement or recognize W3C Semantic Web technologies. This refusal protects Google's proprietary search and categorization algorithms, but it opens the door wide for Microsoft Office editors to totally exploit the end-user semantic interface opportunities. If Microsoft can pull this off, they will take "search" to the Enterprise and beyond into every high end discipline using MSOffice to edit Web ready documents (private and public use). Also a bit about WebKit as the most disruptive technology Microsoft has faced since the advent of the Web.

docs.google.com/Edit - Preview

webkit microsoft google search Cloud-Computing monopoly ge

Gary Edwards (URL) said: Mar. 05, 8:17 PM\n+1 Chrome! It's excellent, but not for the reasons most would insist are important. Neither is Chrome a disruptive technology. It's not. The real revolution is underneath Chrome in the open source WebKit engine. An engine shared with iPhone, Android, Safari, Palm Pre, Nokia, Iris, RiMM 's Blackberry Storm and KDE. Crossplatform WebKit IDE's now include QT, 280Atlas and Eclipse. \n\nIt is the Apple iPhone that put WebKit on the map, demonstrating a revolutionary document/application model capable of leveraging and pushing the Open Web to be competitive with proprietary initiatives from Adobe and Microsoft. \n\nThe WebKit engine is driving most of the smart devices at the edge of the Web, providing a consistent document rendering and application runtime layer that is highly visual, multi-dimensionally interactive, and fully competitive with the proprietary rich interactive application engines (RiA) provided by Adobe and Microsoft. Near 80% of these edge of the Web devices are based on WebKit.

www.businessinsider.com/the-dud-known-as-chrome-2009-3 - Preview

ge android chrome webkit-chromium google henry-blodget businessinsider

Caught this at Clusterstock and found it to be quite the story! ClusterStock's John Carney focused on how Microsoft was using governemnt muscle to trip up competitors. Now it's Googles turn. From the Wired story: "Then, late in the day, Barnett brought up the two words Google lawyers least wanted to hear: Section Two—as in, Section Two of the Sherman Antitrust Act, which criminalizes monopolies. The Justice Department invoked Section Two to splinter Standard Oil in 1911, break up AT&T in 1982, and prosecute Microsoft in 1998. Now Barnett was signaling not just that the Google-Yahoo deal was dead but that the government saw Google as a potential monopolist. In fact, Barnett insisted, if the deal wasn't substantially changed or scuttled, he would sue within five days. It was a stunning blow. Google had expected a speedy approval. Now the company, whose brand is defined by its "Don't be evil" slogan, faced the prospect of being hauled into court on an antitrust charge. Google and Yahoo tried to salvage the negotiations, but on the morning of November 5, three hours before the DOJ was going to file its antitrust case, they abandoned the deal."

www.wired.com/...ff_killgoogle - Preview

Microsoft google anti-trust yahoo