advice for using async vs promise

[joprice]

I'm curious when one should write code targeting async vs JS.Promise. Is it generally advised when writing fable to stick with async and only use Promises at the "borders" when interacting with js-specific libraries, making more of the code usable cross-platform? And is there a performance difference there, or is the async implementation pretty low overhead compared to using promises directly?

Also, on the backend, when using a library like oxpecker, task seems to be preferred in the examples, but I'm not sure of the state of task support in fable as well.

Is there a general recommendation that has good balance of maintenance and performance?

[MangelMaxime]

Personally, I always use promise when possible because they are native the platform so the behaviour is well known, and then can be pass to arbitrary JavaScript code.

I don't think there much of performance penalty for using async if this is what you prefer.

Task is not supported yet by Fable JavaScript but is by Fable Python. There was a discussion for adding support for them to JavaScript too, but we didn't get it done yet. If we were, to add them it seems like we would benefit from both world because Task seems to be hot like Promise.

So it means that we could write use task to write cross platform code, but they would be native to the runtime as in JavaScript we would just translate them to promise.