3 ms·
Wow, this is fantastic. After a couple years of heavy use, I abandoned GWT during the lost-its-marbles insanity of MVP and and what appeared to be a concerted e
by stickfigure 12y ago
Wow, this is fantastic. After a couple years of heavy use, I abandoned GWT during the lost-its-marbles insanity of MVP and and what appeared to be a concerted effort to give GWT all the grace of EJB2.0. I still miss GWT-RPC, dead code detection, static typing, and the sane deployment model. GWT3 could bring me back.
One thing that always bugged me though is the mismatch between Long and JS numbers. GWT is trying to be pedantically accurate with numbers, which is great from a "compile Quake and see it run on the client" perspective but incredibly annoying when trying to interop with native JS code. Many of my ids are numbers; I need these numbers to easily convert to JS numbers - and yes, I do actually know that they will fit within JS precision. Does GWT3 fix interoperability between Java Long and JS Number?