Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Xenon 2.0 suggestions #22

Open
georgechrysanthakopoulos opened this issue Oct 16, 2017 · 3 comments
Open

Xenon 2.0 suggestions #22

georgechrysanthakopoulos opened this issue Oct 16, 2017 · 3 comments

Comments

@georgechrysanthakopoulos
Copy link
Contributor

(feel free to close this and track in Tracker, there might be an item on this already)'

Here some suggestions for next (possibly backwards incompatible) version of Xenon:

  1. Move to and require Java 9.0. Lots of perf benefits (reduction in memory due to new handling of char[] arrays that back strings, others). Also, lots of new syntactic sugar to eliminate for() loops.
    Ahead of time compilation nice bonus for embedded systems that need to faster boot up
  2. Eliminate Netty. Use new, asynchronous Http/2, web socket, server push HTTP client, built in Java!
  3. Add examples using Kotlin. Kotlin runs inside the JVM so will just work with existing Xenon JARs. We just need to show samples. Also, it becomes a viable language for native (no JVM) xenon!

we can meet in person, next time the team is all in Seattle, to discuss this. Or on email.

fyi @asafka @toliaqat @ttddyy

@asafka
Copy link
Contributor

asafka commented Oct 17, 2017

Hey @georgechrysanthakopoulos I'd like to take your offer to meet. I'm actually going to be in Seattle a few days next week, maybe we can meet on Tue (10/24)? anyways, how do I contact you? I can potentially get your contact details from Sufian.

@jvassev
Copy link
Contributor

jvassev commented Oct 28, 2017

Hi George,
We can have Kotlin even now. It is flexible enough to add a xenon-kotlin module in xenon-utils repo.
I've done a POC with xenon and Kotlin's async extensions: https://kotlinlang.org/docs/reference/coroutines.html

I will submit an initial version soon!

Thanks,
Julian

@jvassev
Copy link
Contributor

jvassev commented Oct 30, 2017

Hi @georgechrysanthakopoulos
Have a look at vmware-archive/xenon-utils@f0f8a96

It still needs a lot of love (for example operationContext is not propagated to coroutines) but we can start adding more Kotlin idioms and/or make Xenon more Kotlin-friendly without to much extension methods.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants