These are legitimate concerns and, as such, it is above all a matter of acknowledging the efforts that have been made in this direction, efforts which have not necessarily been successful but which do point to possibilities. In this regard, our cooperative has already established that, as far as the implementation of protocols and formats is concerned, these are always independent of any scheduler (as has been the case since ocaml-tls, see this paper). In this sense, our cooperative has always ensured that our work remains fully reusable by others who do not use our Miou scheduler (this is also very similar to initiatives that have since emerged, such as the sans-io movement).
I would also like to emphasise that attempts have been made to align with picos (which, to my knowledge, has not been done with regard to eio). However, we would like such approaches to take place within a framework that respects the CoC (thereby avoiding insults and defamation, which we have unfortunately had to face).
If such a framework exists and if people wish to build on what has already been done here and here (and thus formally agree on Trigger and Computation), we have no problem devoting our energy to this matter.
As far as we (the members of the MirageOS core team) are concerned, the Eio team has never included us in any discussions aimed at reaching agreement on the possibility of creating unikernels with this scheduler. And although some people wear several hats in this matter, Eio has never reached a consensus within the MirageOS core team (whether on task management policy or on the issue of capabilities). It seems there is no consensus within the community either.
Miou then came along, and I can confirm that it is now possible to develop proper unikernels (even a website) using it without too much difficulty (see our tutorial).
This topic is interesting because I really see it as a re-emergence of what has been criticised on several occasions regarding Eio, and above all it highlights an inability on the part of those involved to collaborate beyond the confines of their own companies. Other actors are therefore turning to developing their own solutions or use what it already exists, having failed to find anything close to what they’re hoping for in Eio. Perhaps it’s time to accept the criticism (whether technical or interpersonal).