You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we are a bit more clear about the backend / frontend, we could indeed promote a bit more the use of Coq from node.
There is some stuff to be discussed on how to make the CLI / API more user-friendly, but indeed it seems there is quite a large demand for such a thing, so hopefully we can tweak the node packages a bit more.
Something that may indeed be nice about node.js is that we are not bound to the JS version of Coq, node could for sure use a native one.
The text was updated successfully, but these errors were encountered:
Now that we are a bit more clear about the backend / frontend, we could indeed promote a bit more the use of Coq from node.
There is some stuff to be discussed on how to make the CLI / API more user-friendly, but indeed it seems there is quite a large demand for such a thing, so hopefully we can tweak the node packages a bit more.
Something that may indeed be nice about
node.js
is that we are not bound to the JS version of Coq, node could for sure use a native one.The text was updated successfully, but these errors were encountered: