Any chances on releasing an update soon?
Cheers,
Mark
We typically wait until the official "gold" release of Firefox is
pushed, because otherwise, we keep having to do new builds everytime a
new RC is pushed.
- a (Google)
Secondly, if you are so concerned check the svn version, build it and
distribute. Don't forget this an open project lead by google not owned
by google. Remember it's Gears, not Google Gears.
Sent from my iPhone
On Jul 2, 2009, at 11:23 AM, Explorer5 <andrew...@gmail.com> wrote:
>
> Did Google even begin development of the Gears plugin for FF 3.5 prior
> to the final version being released? This is so frustrating. How can
> we depend on a technology that a company is pushing when they dont
> even keep up with their own development of it?
>
> C'mon Google!
>
> Even Microsoft would do better than this by at least posting a "Beta"
> or "developers" version of it.. A term which Google should be quite
> familiar with.
>
> -Andrew
>
> On Jul 2, 11:52 am, Ivan <ilissen...@gmail.com> wrote:
Why can't Google test against Release Candidates? The message posted
here before was absurd, something along the lines of "We don't test
against release candidates because then if something changes, we'll
have to alter our code, so we wait until it's released." (I'm
paraphrasing, but that was the gist, I think).
I'm a huge fan of Gears, I think it's one of the most underpromoted
tools of the Internet, and with the ability to run full web
applications offline, it's ideal for smart phone apps. I have it
enabled for my Google tools, Wordpress Admin, and one of our websites.
But a couple of things are shaking my faith in Gears.
The blog hasn't been updated in a long time (the last entry reads
"Gears 0.5.21.0 Released, May 28, 2009 Posted by Ian Fette, Gears Team
In conjunction with Google I/O we're releasing a new version of Gears,
0.5.21.0....)
The featured Articles on the developers page shows articles from 2007.
Some of those articles reference tools and sites that no longer
exist.
And of course ignoring a major Firefox release. Well, not ignoring
it, just not making it a priority, and ignoring the developer
community by not saying anything. How about a message on the blog
saying "We're working on it"? That would go a long way toward
restoring my confidence that I'm not betting on a dying technology.
I can't believe technology this amazing looks like it's withering on the vine.
Tac