The executive summary is as follows. It looks great, it has some cool looking functionality that looks like it may be good to use.
Unfortunately, it seems to have been implemented but people with a great understanding of graphical design and little understanding of programming as a whole. (Think HTML, they knew what they wanted, just didn't know how to ask for it)
The other great bugbear is that the "Open Source Curse" as I have decided to call it. This being that some guys have implemented some stuff, but only the stuff that they use. If you go outside of that scope, you will find that you are the guy implementing a heap of work, but you are stuck with the shit that everyone else has done too.
My usual experiences with Open software is that I come on board late in the picture, when lots of stuff is already done.
This is not the case with the GWT-ExtJS stuff atm. The frame of what is implemented (and actually works) is not far past the minimum for anything that is usable.
The API is horrible and completely different to other Java bases UIs. (Seriously, how hard would it be to make the API match that of SWT.)
So the final word is don't use it. Don't tell people to use and don't make me use it.
It is not complete enough, and it is not good enough, especially when compared with its contemporaries.
The other great bugbear is that the "Open Source Curse" as I have decided to call it. This being that some guys have implemented some stuff, but only the stuff that they use. If you go outside of that scope, you will find that you are the guy implementing a heap of work, but you are stuck with the shit that everyone else has done too.
My usual experiences with Open software is that I come on board late in the picture, when lots of stuff is already done.
This is not the case with the GWT-ExtJS stuff atm. The frame of what is implemented (and actually works) is not far past the minimum for anything that is usable.
The API is horrible and completely different to other Java bases UIs. (Seriously, how hard would it be to make the API match that of SWT.)
So the final word is don't use it. Don't tell people to use and don't make me use it.
It is not complete enough, and it is not good enough, especially when compared with its contemporaries.
1 comment:
So I just re-read this, and it seems that I was well and truly in a fit of despair and anger when I wrote it.
I realise now that the impression I really want to give is that gwt (and more specifically gwt-ext) is a good enough technology if you are planning a here-is-the-church-here-is-the-steeple type application and that is fine.
It is only if you want to step up out of the gutter, use more than three kinds of flair, rise up to the challenge of our rivals and slash or do more than the absolute minimum, to create something that you actually proud of, then you need to look here or here or even here just don't bother going there.
Post a Comment