GXT: not even once

I haven’t posted on GXT in a long time but while discussing its pitfalls with some new teams the other day one of my colleagues came up with a great analogy. Really, GXT is like Meth: you only realize how bad it is once you’ve used it and suffered the consequences, but really we want people to take our word for it and be spared that pain! Hence anyone’s who’s found themselves in the bowels of debugging some terrible, blue GXT widget will appreciate this! Thanks to The Meth Project for helping me out.

  1. #1 by Steve on February 3, 2011 - 9:15 pm

    This is exactly how I feel every time I find a GXT bug and then find that I can’t extend the class because everything in it is PRIVATE. I end up having most of the source code of GXT in my application because there are so many stupid things like that that just can’t be worked around without changing the bloody source code. I wish those bastards at Sencha had to use their own product without having any influence over it’s design!

    Lucky for me I’ve found a couple of days work in GWT 2.0 is all it takes to pretty much replace GXT entirely. DIE GXT DIE!!!

  2. #2 by Alex on February 15, 2011 - 12:18 pm


    This is SO TRUE!

  3. #3 by Davir Roussel on July 17, 2013 - 9:54 am

    Are things any better with GXT 3.0?

    Did the slowness get fixed with the port to pure java? I’ve done a bit of SmartGWT and thought that the mix of JS and java (GWT) was a pain, but what GXT 3.0 is doing looks better.

  4. #4 by Edward on April 22, 2015 - 4:32 am

    I blog often and I seriously thank you for your content. This article has truly peaked my
    interest. I’m going to bookmark your site and keep
    checking for neww information about once a week.

    I subscribed tto your RSS feed too.

(will not be published)