Skip to content

Commit 1383810

Browse files
authored
Update blog post on compliance improvements and VM changes
Clarified the rationale for moving from TeaVM to ParparVM for JavaScript support, emphasizing the benefits of a unified VM for Codename One developers. Signed-off-by: Shai Almog <67850168+shai-almog@users.noreply.github.com>
1 parent cc5466f commit 1383810

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/website/content/blog/compliance-improvements-simulator-updates-and-more.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ This is probably the most important feature this week, but it isn't something mo
9292

9393
Right now this has no impact on you. When you send a build or use Playground/Initializr, you would still use TeaVM and its port. So why are we doing this?
9494

95-
TeaVM is a fantastic project. But it's heading in its own direction, which is different from ours. They are focusing on WASM which is not our choice. WASM makes sense if you want to write deep native code, not if you want to write UIs or front-end. We could fork TeaVM, but that would mean maintaining another port.
95+
TeaVM is a fantastic project. But its heading in its own direction, which is different from ours. We decided to consolidate the different ports to enable a singular portable consistent experience for Codename One developers.
9696

9797
The value of maintaining a single VM that supports all the non-Java ports is powerful. By using ParparVM for our JavaScript port, we can move our support for Java language features at our own pace.
9898

@@ -102,4 +102,4 @@ I spent a lot of time this week on the issue tracker going through old issues. A
102102

103103
It also stands for issues that are important to you and got buried under the mountain of issues. If there are any of those, then let us know. We won't fix a lot of those. Some issues are just out of scope, and our scope is already huge. A lot are just too old by now, and it's hard to tell what's going on. But we're doing our best to go through that list.
104104

105-
Over this past week we closed over 30 issues, but there are still over 500 open issues. We'd appreciate your help in reducing these.
105+
Over this past week we closed over 30 issues, but there are still over 500 open issues. We'd appreciate your help in reducing these.

0 commit comments

Comments
 (0)