GWT Chrome dev OOPHM is Slow. What is the roadmap?

[Brandon Donnelson]

Please focus on the development plugin for Chrome. What is the future roadmap for the Chrome dev plugin?

Thanks,

Brandon Donnelson

[Brandon Donnelson]

I filed a specific issue related to this - http://code.google.com/p/google-web-toolkit/issues/detail?id=6813

[gwt.user]

I suspect this wont change anytime soon because of all the sandboxing chrome does.

[Jens]

Using the development build of Chrome (Chrome Dev Channel, currently version 15.0.874.15) I found its already a good portion faster than it was some time ago. Maybe you can try and update your version.

-- J.

[Brandon Donnelson]

Thanks for that note. I'll check that out. I also added to the issue for reference.

Brandon

[Jens]

Also if you are using Mac you can still use Safari 5.0.5 (or OmniWeb) beside Safari 5.1. Firefox 6 is also supported (search for Firefox 6 in this group and you will find an updated dev mode plugin).

[Brandon Donnelson]

I would say the dev channel release is, "maybe slightly faster". Not even close to as fast as safari dev plugin is. 

Just to make sure, I'm not talking about load time of the dev (translating). Once its up in running, its the widget init and iteration rendering that is slow in chrome compared to safar dev.

Brandon

[Brandon Donnelson]

Chrome canary is the same. 

[Strelok]

Latest ChromeDev (17.0.942.0 dev-m) is unbearably slow. I've given up on Chrome now. Only Firefox is any good on Windows.

[Brandon Donnelson]

If you haven't already starred the issue, please star it. http://code.google.com/p/google-web-toolkit/issues/detail?id=6813 They have begun working on it too. I agree Firefox is faster as of now.

On Nov 27, 2011 6:39 PM, "Strelok" <roman...@gmail.com> wrote:

Latest ChromeDev (17.0.942.0 dev-m) is unbearably slow. I've given up on Chrome now. Only Firefox is any good on Windows.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/8d9-qD1kvWwJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Tom Carchrae]

I'm curious to know why this is a priority for you?

I use Firefox for development and it's a perfectly workable solution for me.  What does Chrome give you that you need for GWT development?

Tom

[Williame]

I am a linux dev, my ubuntu distro updates firefox along with the OS updates soon after a new firefox release.  Mozilla has adopted an aggressive release schedule and the gwt plugin for it has lagged several weeks behind.  So when a new firefox is released, i have to change from firefox dev to chrome dev until the plugin is available for firefox.  I have yet to have a google chrome version update break the gwt plugin, or ot have an updated plugin available immediately.  I can count on chrome on linux with the gwt dev plugin(YAY!!).  It's just really, really slow for non-trivial page layouts.

Otherwise, my options are run a local, older version of firefox I download and hope the latest firefox doesn't update the shared prefs/plugins breaking the older version I'm running alongside it or reboot into windows and develop there.

GWT, besides being AWESOME, is a free product so I don't have a leg to stand on to complain to Google.  But I do humbly request they get Chrome up to firefox speed in gwt dev mode.  Pretty please.

It is ironic that the gwt plugin for chrome, both Google products, is the slowest combination.

Thanks

[Jeff Chimene]

On 11/28/2011 09:47 AM, Williame wrote:
> I am a linux dev, my ubuntu distro updates firefox along with the OS
> updates soon after a new firefox release. Mozilla has adopted an
> aggressive release schedule and the gwt plugin for it has lagged several
> weeks behind. So when a new firefox is released, i have to change from
> firefox dev to chrome dev until the plugin is available for firefox. I
> have yet to have a google chrome version update break the gwt plugin, or
> ot have an updated plugin available immediately. I can count on chrome
> on linux with the gwt dev plugin(YAY!!). It's just really, really slow
> for non-trivial page layouts.
>
> Otherwise, my options are run a local, older version of firefox I
> download and hope the latest firefox doesn't update the shared
> prefs/plugins breaking the older version I'm running alongside it or
> reboot into windows and develop there.

You're comfortable with installing FF locally? When installed as root,
but run as non-root, it will not automatically update the existing version.

FF can be configured to not check automatically for updates.

The GWT plugin can be installed on a non-root basis.

If the above doesn't float your boat, consider using
update-alternatives
(http://manpages.ubuntu.com/manpages/lucid/man8/update-alternatives.8.html)
to manage two versions: latest and a lagging development version.

> GWT, besides being AWESOME, is a free product so I don't have a leg to
> stand on to complain to Google. But I do humbly request they get Chrome
> up to firefox speed in gwt dev mode. Pretty please.

There are some technical issues w/r/t to Chrome speed matching FF. There
are several threads in this group discussing the issue. The gist is that
the Chrome devs have to implement some features.

> It is ironic that the gwt plugin for chrome, both Google products, is
> the slowest combination.
>
> Thanks
>

> --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/google-web-toolkit/-/h5XPdl9EskcJ.

[John Ho]

While I can't speak for the OP, I'll add my two cents on why it would be a major plus for our development team. We are developing an offline feature using Web SQL and the only way to test it is to go through Chrome, since Firefox does not support it.

[David Vree]

@jchimene -- thanks for that...hugely helpful as I dev on Ubuntu and the constant Firefox updates are a pain.