TeaVM Vs Endive #5098
Replies: 1 comment 1 reply
-
|
We're retiring TeaVM and moving to our own custom JavaScript front end based on our own VM. Notice that it isn't because TeaVM isn't fantastic (it very much is), it just moves in its own direction and we need more control. As far as I understand Endive has nothing to do with TeaVM and it looks like a pile of ... Endive is WASM embedding. WASM is a piece of crap that has no valid reason to exist outside of the browser. Embedding it into Java is just about one of the dumbest ideas going around: let's embed an inferior cross platform solution into my proven cross platform solution.... Right brilliant. Their one excuse is that you "won't have to use native code" because you can compile C or Rust to WASM... That is one of the biggest lies ever. Sure you can run Doom on it, but normal code that works with real world things (like threads) would be tough, there are solutions but every one of those solutions makes things worse and at a x2 performance overhead where you can just take the damn native code and run it and it wouldn't be as complex. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey @shai-almog, I was reading the post about Endive, it looks like it will have more community support than TeaVM (Just opinion, I think that only time will tell), do CN1 have any plan to migrate?
Besides that, there's any way to build for js locally?
Beta Was this translation helpful? Give feedback.
All reactions