@Ivan Markov For some reason I cannot edit my previous message :-( Just
want to clarify that I'm extremely grateful for your SDBG tool, it's
beautiful software, and it's really sad to hear that you have some doubts
about it.
On Monday, June 11, 2018 at 7:35:47 PM UTC-7, Slava Pankov wrote:
>
>
@Ivan Markov Please invest some time to SDBG, it's great tool, very
convenient. Despite of Chrome dev.tools, I still prefer SDBG as more
natural for java developer.
On Thursday, May 31, 2018 at 6:02:43 AM UTC-7, Ivan Markov wrote:
>
> Don't you think there could've been 2x or even 3x as much
J2CL is yet-to-be open-sourced Google product, I'll post a separate update
on the state but that's why it wasn't developed openly.
GWT, which is community owned; there is nothing done in secrecy and people
in the community actively working on GWT 3.
On Sun, Jun 10, 2018 at 3:58 AM Norbert Sándor
Wow! It's great to see all that progress being made on GWT 3. That's a lot
more backwards compatibility than I was expecting.
Still, it would be nice to have J2CL released separately as soon as it is
ready to do so because
1. Based on past experience, it will take 1-2 years or more before
Please send your member requests with some background information on why
you need early access.
On Fri, Jun 1, 2018 at 3:08 PM Julien Dramaix
wrote:
> I changed the permission settings. You should now be able to apply for
> membership at https://groups.google.com/forum/#!forum/j2cl-external
>
>
I changed the permission settings. You should now be able to apply for
membership at https://groups.google.com/forum/#!forum/j2cl-external
-Julien
On Fri, Jun 1, 2018 at 1:50 PM Alberto Mancini wrote:
> Hello Goktug,
> thanks a lot for the opportunity.
> Actually seems that the address
Hello Goktug,
thanks a lot for the opportunity.
Actually seems that the address j2cl-exter...@googlegroups.com does not
exist.
mailer-dae...@google.com
We're writing to let you know that the group you tried to contact
(j2cl-external) may not exist, or you may not have permission to post
Hi all.
Sorry for the delays in getting J2CL work for opensource. Some of the
delays were out of our control but this is something we actively working on
in the last few months and having progress. In the meantime plenty of
active GWT contributors already has access to it for a long time and
Don't you think there could've been 2x or even 3x as much people working on
porting GWT2 stuff over to J2CL if J2CL was released in the first place?
For one, releasing J2CL could've made me reconsider how much time I invest
in my own SDBG pet project. Which - at the current situation is exactly
That's not really true. There are a lot of people working on the GWT
module, getting them out of GWT and moving them to standalone artifacts.
Doing that, they replace JSNI with JsInterop, replace generators, etc. This
is all done, to get GWT 2 ready for GWT 3. And if you want to see something
>
>1. The backing company backed off but kept the crucial new piece
>secret - J2CL.
>
> These days it is already available to a few people who take their spare
time to make it useable by the general public.
>1. The past and current stated direction devolves the product, does
>
gle-web-toolkit-contributors@googlegroups.comReply to: google-web-toolkit-contributors@googlegroups.comSubject: Re: [gwt-contrib] Re: The elusive J2CL Being slow but mature is a pretty good thing sometimes. As you said, "today's rapidly changing IT" is crazy rapidly, you start a project in a t
Being slow but mature is a pretty good thing sometimes. As you said,
"today's rapidly changing IT" is crazy rapidly, you start a project in a
technology that when the project is production ready it might be that
technology considered deprecated already. Java and GWT are all about
maturity and
I would recommend Vaadin instead (of GWT or any JavaScript). If you like
you can use Kotlin or Scala with it as well.
--
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
I have been an enthusiastic user of GWT for many years but I don't use it
anymore and I recommend for everyone not to use it for new projects.
(Additionally I think that Google killed GWT like it did with other
interesting and useful projects.)
Use Javascript, Kotlin or even Doppio
I agree 100% with Ivan, every word he said is true.
You can also rewrite your UI code to work with Vaadin (8 or 10 soon) and
all the rest of your code (business logic, persistence, services) can stay
(almost) the same as it is now in your GWT. Vaadin 10 (Flow) will be ready
soon, it does not
While waiting for our moderator (probably from USA) to wake up, here is a
link with today's news about Vaadin
10: https://vaadin.com/blog/vaadin-10-beta
It explains what it is so you can decide if this is something that could be
interesting for you.
Regards,
Marko
--
You received this
17 matches
Mail list logo
