GWT closing panel

The last session in the gwt.create conference was a discussion panel with speakers, GWT steering committee members and participants asking questions.

panel

Here some questions/ answers I managed to write down…

Q: What about Dart, GWT, say in two years?

The point is: GWT is here to stay, and even if Dart becomes the real next huge big thing, GWT will be one way to do it. Daniel reiterates that we should not think of one OR another.

Q: We don’t want to debug in JS in Chrome. Any way to do it better then SuperDevMode?

Well, no. DevMode is going away, and that is not GWT teams fault. Browsers are closing the door to required plugins, JS debuggers and source maps are the way to go.

SuperDevMode is no replacement or DevMode, but it has advantages, hence we start debugging in the target language/ platform. Besides, SuperDevMode is the only way to debug on mobile devices.

We also must take the improvements made by browsers/ debuggers in the past, so there is hope. IntelliJ is working on a remote debugger, nothing is known about Eclipse.

Attendees stated real life issues with SuperDevMode and the thread posed by not having DevMode ready, stable, fast, usable by the time the plugins stop working.

Discussion also showed that adoption might be better if setup is easier. Still, the worst case as described by Ray would be that we cannot use DevMode in the newest browsers – specifically Firefox and Chrome. We must keep in mind that actually DevMode is already broken in Safari and mobile devices.

Q: If you had a magical wand, what would you add/ remove change from GWT?

Nice question, here some statements.
Please don’t take them seriously, as no one really does have a magic wand…  :-)

  • Remove UI binder in favor of a HTML template mechanism
  • Incremental building
  • Vertical and Horizontal Panels (attendees cheer…  :-)  )
  • Kill the Widget system (because it was original made to fix IE6 memory leaks) in favor of a light widget model
  • Remove the “Serializable” interface support for GWT-RPC, as the implications on compilation are huge
  • Add runtime performance. More. Performance.
  • Configuration properties, compiler properties. Properties confusion.

Leave a Reply

Your email address will not be published. Required fields are marked *