Re: [gwt-contrib] The elusive J2CL

A basic functionality missing in open-source build doesn't mean it is far away. We were trying to get it ready by this quarter but it didn't work out as I explained earlier. For 'pure' J2CL experience, we have chosen bazel. Bazel works/scales pretty well and same as our internal setup which makes

Re: [gwt-contrib] The elusive J2CL

Yes, I agree "even basic missing functionalities" sounds scary. And why bazel? It's not even close in popularity with Maven and Gradle. On Friday, March 9, 2018 at 1:52:34 AM UTC-8, Ivan Markov wrote: > > Goktug, sorry for being a but stubborn here, but we need a tad more > visibility: > >

Re: [gwt-contrib] The elusive J2CL

Goktug, sorry for being a but stubborn here, but we need a tad more visibility: {quote} The main blocker for releasing J2CL for wider audience is even basic missing functionalities around building it in open-source and seeing at least some output for your compilations. {quote} "even basic

Re: [gwt-contrib] The elusive J2CL

> There is still tone of work to do for a polished open source experience but at least we can give access to more people who is really interested. What I meant here; is giving access *after* basic bazel stuff is finished so there will be something to play with. We don't want to give access to a

Re: [gwt-contrib] The elusive J2CL

Hello, yes, definitely I would like to be in. I am really interested. Cheers, Alberto. On Thu, Mar 8, 2018 at 2:21 PM Nándor Előd Fekete wrote: > I am *really* interested. Can you sign me up? > > > On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan

Re: [gwt-contrib] The elusive J2CL

I am *really* interested. Can you sign me up? On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote: > > The main blocker for releasing J2CL for wider audience is even basic > missing functionalities around building it in open-source and seeing at > least some output for your

Re: [gwt-contrib] The elusive J2CL

Goktug, We don't want a polished experience. We want *some* experience. :) Is there anything we can help with? BTW, I thought Bazel is already open sourced and you are already building with it? What's the roadblock there? BTW 2: Releasing a J2CL binary would also help, as long as that's

Re: [gwt-contrib] The elusive J2CL

The main blocker for releasing J2CL for wider audience is even basic missing functionalities around building it in open-source and seeing at least some output for your compilations. That is blocked on missing functionalities in bazel. After that we can probably finished in more timely manner.

Re: [gwt-contrib] The elusive J2CL

I posted my message (OK. My rant!) here, because I wanted to get the attention of Goktug, Daniel & the rest of the Google crew. It is a plea to change something ASAP, and if someone could, it is them. As for the rest of your comments... don't know where to start. Most important is, you seem

Re: [gwt-contrib] The elusive J2CL

I am perfectly happy with Java/JsInterop in its current state. Sure there are some things that could be improved, but what couldn't. BTW, I have never used the GWT widgets, so my case may be different. I tried TS, Angular, etc..., and have come back to GWT with JsInterop to deal with large

[gwt-contrib] The elusive J2CL

This time I'll bite... J2CL has been - what? - two to three years in the making - yet, there is nothing released to the public yet (aside from a preview to a few blessed individuals). Before someone follows up again with the usual matra that "it is not production ready yet and it will do more