schedule-x VS wasmer-java

This article will discuss the general concept of building a cross-framework frontend library. It will also display some examples of how this was applied when building the event calendar Schedule-X.

Ah, never even thought of having a kind of overlap tolerance. I might look into if this would make sense for Schedule-X too.

Solving overlapping events was definitely one of the things were a couple of days went into finding a nice and performant solution. My solution is here: https://github.com/schedule-x/schedule-x/blob/main/packages/...

Basically what I do is iterate over a list of events, sorted by start time, and for each:

Great idea! Luckily, there's https://github.com/wasmerio/wasmer-java, so you can easily run that wasm binary in your JVM running in your browser!

The biggest integration library is wasmer. It's intended as a server runtime for wasm. The official port wasmer-java has the problem of not supporting imports and that's also not to be implemented in the near future (they are restructuring the wasmer library according to this issue), the other is wasmer-jni. An inofficial jni-binding for the wasmer base implementation. Less nice to use, but feature complete.

Check how the rust compiler can target Web Assembly and then have a look at https://github.com/wasmerio/wasmer-java

If your savvy with WASM I think you could compile to wasm and make java bindings with https://github.com/wasmerio/wasmer-java