On Thu, May 27, 2021 at 5:52 PM Vassilis Virvilis <firstname.lastname@example.org> wrote:
That supersedes elemental2. And the API is not the same (AFAICT) so we are going to have some inevitable churn in our code base.
The APIs are different but not substantially so - it took us a couple of hours to convert our code bases which are mid-sized.
Will this be endorsed by GWT as elemental2 replacement?
No idea - I also dont know who GWT is ;) Google has a large internal closure code base so it is unlikely that they will adopt as the externs differ. The akasha externs are more strongly typed to try and get slightly better optimizability by CC and if you don't have an existing closure codebase this is an easy win but not so if you have a large existing js codebase.
I tried to find the gitnub page for the project (found it: https://github.com/akasha/akasha) but https://github.com/AKASHAorg pops up.
I should have popped that in the email ;)
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc5X6EnxcqUyEgSY07YrJWxcggnnV1qC3dEAir1Y%3DDJGbw%40mail.gmail.com.
Post a Comment