Re: Teavm

Source maps from byte code? El martes, 1 de diciembre de 2015, 16:43:44 (UTC+1), Satguru Srivastava escribió: > > So, I recently came across TeaVM (http://teavm.org/) > Similar to GWT but unlike GWT, which compiles Java Source Code to > JavaScript, TeaVM compiles Java Byte Code t

Re: Teavm

Srivastava escribió: So, I recently came across TeaVM (http://teavm.org/) Similar to GWT but unlike GWT, which compiles Java Source Code to _javascript_, TeaVM compiles Java Byte Code to _javascript_

Re: Teavm

tooling for a statically-typed language is > different from / can go farther than for a dynamically-typed one), and > sharing code. > > > >> For me TeaVM has completely different approach to the problem than GWT - >> it allows language agnostic web application development

Re: Teavm

On Thursday, December 3, 2015 at 12:24:38 PM UTC+1, Martin Trummer wrote: > > there is an old group post > > > that already discusses the byte-code vs. source code issue - maybe it is > still

Re: Teavm

> That said, browser-specific permutations has IMO reached a dead-end: > Microsoft will stop support IE<11 in 40 days or so (except IE9 on Vista), > which means that we'll have (hopefully) almost everyone using a "modern > browser" where discrepancies aren't that many and can be dealt with at >

Re: Teavm

I do not know if permutations have reached a dead-end but i find that 'static' (in the sense related to the browser user agent) detection is going to be hard to maintain. Each new version of a browser (and the update is largely automatic) may change the support so compiling for a specific user

Re: Teavm

I don't see how you can easily support and maintain something like web-components (where different Browsers implement different parts of the spec) using browser specific permutations. With Edge almost all browsers vendor follow a relatively fast release cycle (ok Safari is the new IE in this

Re: Teavm

ten us, . TeaVM. I guess, is a way to find that out . Add benefits of byte-code compilation and TeaVM becomes whole lot more interesting On Thursday, December 3, 2015 at 5:24:38 AM UTC-6, Martin Trummer wrote: > > there is an old group post > <https://groups.google.com/forum/#!msg/

Re: Teavm

been about tooling: http://www.gwtproject.org/makinggwtbetter.html Now that tooling is quite good in the JS world, GWT is turning to… tooling, still (because tooling for a statically-typed language is different from / can go farther than for a dynamically-typed one), and sharing code. > For me Tea

Re: Teavm

> Since the end result is JS, can i use cordova to cook up a mobile app > using TeaVM? > You can try to. I'm not sure I've cleaned up any browser-specific APIs from TeaVM runtime. Please, report me if you have some success with cordova. However, I don't think it's a

Re: Teavm

> > Not sure if TeaVM serves different need than GWT. Seems like both want to > provide a better alternative to JavaScript. > Now TeaVM does not have anything equivalent to GWT widgets but then it > seems, after watching the GWT Create session videos, the recommendation, &

Re: Teavm

> > - virtually this is one pony show - except Alexey there are no major > contributors (nothing against Alexey of course he is brilliant guy) > Yes, this is the worst problem of TeaVM. I wonder how do projects become popular? If a project is maintaned by a big and rich company,

Re: Teavm

anyway. The whole purpose of using GWT/GWTP was to avoid to deal with JavaScript, at least in my case. For me TeaVM has completely different approach to the problem than GWT - it allows language agnostic web application development (I never liked GWT no prisoners taken approach - Java or nothing

Re: Teavm

Hello Alexey, Since the end result is JS, can i use cordova to cook up a mobile app using TeaVM? Thanks, Subhro. On Wed, Dec 2, 2015 at 3:47 PM, Alexey Andreev <konsolety...@gmail.com> wrote: > - virtually this is one pony show - except Alexey there are no major >> contri

Re: Teavm

I feel your pain - too bad that everybody are so hell bend to develop "better mouse trap" in JavaScript so they are lost sight of different ways of doing things. I'm planning to start working on TeaVM in the next 6 months - maybe approach every little bit helps will move TeaVM f

Re: Teavm

Not sure if TeaVM serves different need than GWT. Seems like both want to provide a better alternative to JavaScript. Now TeaVM does not have anything equivalent to GWT widgets but then it seems, after watching the GWT Create session videos, the recommendation, for newer apps, is not to use

Re: Teavm

it to byte code and run it on JVM - you can run it with TeaVM - of course with some reasonable restrictions because of JavaScript nature). However for me there are two major show stoppers for broad adoption in production: - project is still in early growing phase - virtually this is one pony show

Teavm

So, I recently came across TeaVM (http://teavm.org/) Similar to GWT but unlike GWT, which compiles Java Source Code to JavaScript, TeaVM compiles Java Byte Code to JavaScript. It is an interesting approach. The big advantage to this approach is that you do not have to create and maintain your

Re: Teavm

We are using TeaVM for the javascript port of Codename One and have been very happy with the results. One thing that TeaVM offers that nobody else in the Java->Javascript realm is thread support. Performance is also very good, and the creator (Alexey) is quite responsive to support reque