For now, I am trying keep a narrow (and opinionated) scope while the API is shaping up. I want coffee to be great for building (some) games for desktop.
I see WASM support as a nice thing that could happen as a side-effect. I have no clue what kind of compromises need to be made when targeting WASM (any guidance is appreciated!), but maybe a subset of the final API ends up being compatible without too many of them.
That said, I am trying to have clear boundaries between dependencies and engine code, which should help in the future if there is a need to swap a dependency or mock it somehow.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.