molecule VS j2cl

Meanwhile, https://github.com/cashapp/molecule and https://github.com/slackhq/circuit/blob/cfcb6e6a28c53c0715d961917a9a5a9ddc07d5f3/docs/presenter.md?plain=1#L18

Reddit uses Molecule, not Circuit.

You could look at Compose, how the Compose compiler works internally, and perhaps build something unique / non-ui or investigate some other deep aspect of Compose compiler.

Thanks for the links, I already opened a bug issue : https://github.com/cashapp/molecule/issues/136

Today in "HN never used a reactive framework that is not React and is offended when UI is not written with Dear ImGui".

This is literally the exact style of SwiftUI and Jetpack Compose (down to the author having used the term fragment, I sure hope this isn't leftover trauma from being an Android developer), except written in Rust (hence having to deal with lifetimes in the middle, default parameters, lambdas being quite verbose and needing to move things, etc).

Not blocking the UI thread is mandatory if you ever want to make any kind of complex UI. If you're a web dev, well you only have one thread anyways, good luck, if you're on any other platform, interactions _cannot_ ever block the UI (unless you, yourself, update the UI to say it is blocked). Making this async is a good thing.

Stack traces are a problem, but then again they've been a problem in any remotely capable UI toolkit.

With ReactiveCell, it looks surprisingly similar to what Compose does, where modifying a State causes recomposition of everything observing it. Which means that it might be powerful enough one day to do the same things as Molecule (https://github.com/cashapp/molecule), or ComposePPT (https://github.com/fgiris/composePPT), where everything is a potential target and it interops really well with existing toolkits.

Hmm, I see 0.4.0 https://github.com/cashapp/molecule/releases/tag/0.4.0

Here's an example: https://github.com/cashapp/molecule

Recently, Cash App introduced Molecule and suggested that Jetpack Compose can help solve the problem of managing UI state.

There are many open source projects like, https://github.com/google/j2cl/tree/master/samples/wasm

This was a grand stroll down memory lane; having hacked Java since JDK 1.0, I've seen a lot of improvement.

An idle thought: he favors server-side rendering whereas the javascripts seem to favor client-side rendering. Along the way doing servlets, there came to be "view first" rendering, where you use serverside to paint a minimal page which, itself, uses ajax calls to fill in the blanks. I used that a lot.

It's true also that I migrated from servlets to node. But, in all of this, clojurescript erupted on the scene. And, for me, that's where the piece gets interesting: he introduces us to a java to clojurescript transpiler and tells us it was used to craft the google app suite. Now it's time to go play [1]

[1] https://github.com/google/j2cl

So it looks like we have pretty much everything except for the most important part: three.js that we can use from Java. And it’s a little bit of a complex part. To interop with JavaScript we should use J2CL JsInterop API, but there is a little problem: Closure Compiler must be able to recognize types of (most of the) three.js objects. Here we have two options:

You mean https://github.com/google/j2cl ? You understand though that these are trying to solve multiplatform in very different ways. I don't think this approach has a bright future.

Have you seen J2CL? https://github.com/google/j2cl