3 messages in com.googlegroups.google-gearsRe: Feature request: Google should in...| From | Sent On | Attachments |
|---|---|---|
| fgs | 31 May 2007 08:10 | |
| Martin Porcheron | 31 May 2007 08:25 | |
| eAi | 31 May 2007 08:28 |
| Subject: | Re: Feature request: Google should invest more resources into this |
|---|---|
| From: | Martin Porcheron (mart...@gmail.com) |
| Date: | 05/31/2007 08:25:12 AM |
| List: | com.googlegroups.google-gears |
Hi,
Here's how I see things:
1) Google has open-source the code so that other people can take the source, make modifications and even suggest them to Google. 2) Because this is so early on in the dev. cycle Google is most probably working on Bug fixing and implementing (hence the widespread test of this on Google Reader - before it hits the market on main Google products such as Gmail). I believe Google is also planning to suggest Google Gears to become a standard in web browsing (yay!). 3) O'Reilly doesn't need sponsoring, they will write one anyone as they do with most emerging web technologies It won't come yet though, we're only on release 0.1x. 4) In due course this will most definetly come. Google will most probably integrate it into all the Google Apps products (eg, Gmail, Calendar etc). 5) The fact that this hasn't been done before and is already creating quite a stir on technology blogs isn't a big enough incentive?
Martin
On 5/31/07, fgs <s.de...@gmail.com> wrote:
This Google Gears is very important for Google and the computer industry. Therefore, I believe Google should spend as much as possible resources on this (IMO this is at least as much worth as Youtube if you want an indication of th amount of resources ;-) ). Examples: 1) Form an *independent* organization that coordinates development of Google Gears technology 2) Make it as userfriendly possible for both commercial and open- source projects to integrate this technology (excellent docs, clean code/API, libraries for multiple programming languages,...) 3) Create/sponsor an O'Reilly book for coders that want to use this technology 4) Add support in any Google application 5) Give more incentives to instances for adoption of this technology