I understand GWT-RPC would be interesting at least for some people but that still doesn't make it a trustworthy, decent RPC system and has fundamental flaws which we have enumerated couple of times already. I see it could be potentially replaced with something more sane and useable but like some others have already suggested it seems like the replacement is better to evolve and mature independently and later evaluated to see if it is part of compatibility lib or something we can recommend for future development.
On Thu, Oct 18, 2018 at 4:16 AM Learner Evermore <[email protected]> wrote: > I strongly disagree that this should be just a compatibility library. > Thomas, will all due respect, if you don't find it useful for your work it > does not mean others don't and REST APIs are seeing their own sunset as > well and JavaScript approaches come nowhere near where they need to be to > cover the points I listed. Even if I could expose APIs of any other kind > (REST, GraphQL, JavaScript/JSON or not) the "GWT RPC (NG)" still has a > great place, perhaps parallel (in addition to them) for all the reasons > listed. RPC was what completed the GWT value proposition - without it it > isn't much better (if at all better or even close to) than a number of > other solutions out there and doesn't fulfill its own promise. Instead of > performant abstraction we'd have a thin translator requiring the developers > to continue to know and think about both Java and JavaScript world of > things. > > JavaScript is an *awful* language and system in any of its incarnation for > anything complex. Arguments that it is the best because of performance, > size and library availability are the same as those used for assembly and > Fortran a while back and are pointless, especially due to the prospect of > WebAssembly. In my opinion, GWT should completely abstract that platform > and be able to, eventually, leverage whatever is the best for it without > impacting the apps built using it. As such, abstracting JS away as much as > possible is a benefit just like it is using the paradigms of the core > language of GWT - Java. > > Learner Evermore > > > Original Message > From: [email protected] > Sent: October 18, 2018 3:17 AM > To: [email protected] > Reply to: [email protected] > Subject: [gwt-contrib] Re: "GWT RPC" and its role in the future of GWT > > Everyone knows I don't like GWT-RPC (specifically related to some of the > points "Learner" listed), but I cannot deny that it's been a big selling > point of GWT over the years. > For that reason alone, I won't oppose to it being in the org.gwtproject > namespace. So let's do that (but IMO make it more a "compatibility lib" for > those coming from GWT 2, replacing its use in tutorials and samples with > something else -- RESTish JSON APIs are easy nowadays with JsInterop, so > probably use that instead, as that makes it easier to understand that GWT > could be used with any backend) > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/7785d7c8-4f2e-4d95-9ea9-b287c0b65544%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/2shv5gsgoe900hgcebeo5p86.1539861391103%40gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0WfeX%3DpJ_BDNf5MBwD%2Bm2-107o5DsbkWqkgx4bevaErw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
