Remove JVM target #8582
Closed
Remove JVM target #8582
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We had an internal discussion about this and agreed to not drop the target after all. Some team members judge JVM as a Haxe target more positive than I do, so for now we're going to keep it as a low-priority target. We're going to discuss our strategic focus regarding all this and hopefully come up with a clear plan. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is gonna make me look bad no matter what, but I'll try to explain anyway. I was working on a JVM target as a hobby project over the years and just so happened to reach a working state earlier this year. My original motivation for this was twofold:
Unfortunately, neither of these are working out. The current Java target actually performs better overall than the JVM target due to some intricate optimizations. Furthermore, the JVM target relies on some API which is unavailable on some android devices, so the current Java target is still needed.
I apologize for any inconveniences this causes, but I would like to pull the plug on this while we still can. We have enough code to maintain already and adding more targets is only going to make this worse. If anyone wants to pick this up and maintain it in the future, I'll be happy to help with that.