This is great. This is actually fairly similar to something I've been thinking about doing for some time, so I have a few comments to make! For a previous job I wrote a miniature/lightweight "actor system" with haskell threads and STM. Basically, each actor was represented by a thread, threads operated in a loop (like erlang actors), and threads had mailboxes implemented via STM primitives. It worked like a dream, an…
Butler Virtual Operating System
11–18 of 18 posts
Re: Butler Virtual Operating System
#12This is great. This is actually fairly similar to something I've been thinking about doing for some time, so I have a few comments to make! For a previous job I wrote a miniature/lightweight "actor system" with haskell threads and STM. Basically, each actor was represented by a thread, threads operated in a loop (like erlang actors), and threads had mailboxes implemented via STM primitives. It worked like a dream, an…
You may be interested in https://discourse.haskell.org/t/towards-an-actor-framework-f... , then!
I actually had started working on modernizing the cloud haskell code, but just realized it was far more work than I had time to put towards it at that time. I'm trying to get some things complete so I can focus on some other things instead, such as contributing towards this =)
Assuming you are the same NicholasT, if you want I can share some of the code snippets that I used to implement what i'm talking about. I just know that I can't commit any significant time toward this right now though.
Re: Butler Virtual Operating System
#13This is great. This is actually fairly similar to something I've been thinking about doing for some time, so I have a few comments to make! For a previous job I wrote a miniature/lightweight "actor system" with haskell threads and STM. Basically, each actor was represented by a thread, threads operated in a loop (like erlang actors), and threads had mailboxes implemented via STM primitives. It worked like a dream, an…
As someone interested in pursuing similar ideas I would recommend taking a look at Object Capabilities and the E Language if you haven't already. I believe Sandstorm.io (and Cap'n Proto) at least adopts some of the ideas.
I suspect one of the things Sanndstorm did that probably caused it issues was was biting off too much, for example implementing its own linux containers system (I don't know what the details were, I just know that at the time, I was thinking "if it were me, I would just use docker.")
Re: Butler Virtual Operating System
#14Earlier quoted context omitted.
You may be interested in https://discourse.haskell.org/t/towards-an-actor-framework-f... , then!
Thank you, I am! I saw this linked in the original post. I actually had started working on modernizing the cloud haskell code, but just realized it was far more work than I had time to put towards it at that time. I'm trying to get some things complete so I can focus on some other things instead, such as contributing towards this =) Assuming you are the same NicholasT, if you want I can share some of the code snippet…
Re: Butler Virtual Operating System
#15Choosing HTML for UI subsystem of an operating environment is refreshing. Is there a demo URL?
https://en.wikipedia.org/wiki/Active_Desktop
Re: Butler Virtual Operating System
#16Earlier quoted context omitted.
https://en.wikipedia.org/wiki/Active_Desktop
Active desktop was not a proper UI subsystem for apps. It was just a "content" on the Desktop and maybe in some folder views with appropriate desktop.ini file.
Re: Butler Virtual Operating System
#17Earlier quoted context omitted.
Thank you, I am! I saw this linked in the original post. I actually had started working on modernizing the cloud haskell code, but just realized it was far more work than I had time to put towards it at that time. I'm trying to get some things complete so I can focus on some other things instead, such as contributing towards this =) Assuming you are the same NicholasT, if you want I can share some of the code snippet…
I am indeed. Feel free to reach out, would be happy to learn from the approach you took.