In the scale of thing the Java -> WebAssembly is probably relatively easy bit? Even after very tough problems like GC and host/JavaScript binding there would be no Widget set etc? I'm also a massive fan of Editor/RequestFactory etc that have magic in the complication process that I don't think anyone is offering to support.
I think Thomas is right. GWT 3.0 is going in the direction of playing nicely with all the other JavaScript toys nicely. However, I'm in the other main camp that wants to program in Java using a component based widget set where the browser is just another deployment target. I could be wrong about the "other main camp", could just be me ;) Regards Sam On Tuesday, September 26, 2017 at 4:10:57 PM UTC+1, Kirill Prazdnikov wrote: > > TeaVM is capable of Java to WebASM translation. > > However you must understand that WebASM can not access to > > * DOM > * Network > * WebGL > * WebAudio > * GC > * Any JavaScript Object > > It can only do [+, -, *, /, read, write] of [int8, int16, int32, int64, > float32, float64] and make calls to JavaScript methods with simple nuberic > signature like Math.sqrt. Also it can make calls. > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
