Message Passing and the Actor Model
dist-prog-book.com
Message Passing and the Actor Model
1–10 of 88 posts
Re: Message Passing and the Actor Model
#2I was hoping to see a mention of Pony which looks like a promising language based on the actor model.
Re: Message Passing and the Actor Model
#3I was hoping to see a mention of Pony which looks like a promising language based on the actor model.
Pony does look really solid. It's still new however. Give it 4 years or so.
Re: Message Passing and the Actor Model
#4Is there an index to this book I'm not seeing? I see the directories, but not seeing an overall index. A bit hard to navigate.
Re: Message Passing and the Actor Model
#5I was hoping to see a mention of Pony which looks like a promising language based on the actor model.
Pony does look really solid. It's still new however. Give it 4 years or so.
When I took Pony for a test drive, the language itself felt pretty solid; the main obstacle was the tiny standard library.
When Pony's standard library grows to a useful size, it's going to be huge. The type system is gorgeous, the documentation is pretty good, and the community is extremely friendly and helpful.
Re: Message Passing and the Actor Model
#6> 59 minutes read
Is this actually correct? I am inclined to think not but it is difficult to judge just from scrolling through it quickly.
Re: Message Passing and the Actor Model
#7Earlier quoted context omitted.
Pony does look really solid. It's still new however. Give it 4 years or so.
When I took Pony for a test drive, the language itself felt pretty solid; the main obstacle was the tiny standard library. When Pony's standard library grows to a useful size, it's going to be huge. The type system is gorgeous, the documentation is pretty good, and the community is extremely friendly and helpful.
It sounds like the type system is going to get more featureiferous; my understanding is that they are pushing towards actual dependent typing.
Re: Message Passing and the Actor Model
#8Earlier quoted context omitted.
When I took Pony for a test drive, the language itself felt pretty solid; the main obstacle was the tiny standard library. When Pony's standard library grows to a useful size, it's going to be huge. The type system is gorgeous, the documentation is pretty good, and the community is extremely friendly and helpful.
It sounds like the type system is going to get more featureiferous; my understanding is that they are pushing towards actual dependent typing.
I wish I could target the browser too. Like my biggest problem is writing a front-end and backend in two languages. If I could do both in one, that would be such a killer feature.
Re: Message Passing and the Actor Model
#9Is there an index to this book I'm not seeing? I see the directories, but not seeing an overall index. A bit hard to navigate.
If you click on "Chapters" it takes you to a directory listing of the chapters, click on a chapter link and it takes you to another directory listing of pages. Click on a page link and it takes you to an actual chapter.
It appears that the "book" still needs a fair amount of polishing to be navigable.
Re: Message Passing and the Actor Model
#10Earlier quoted context omitted.
It sounds like the type system is going to get more featureiferous; my understanding is that they are pushing towards actual dependent typing.
I wish I could target the browser too. Like my biggest problem is writing a front-end and backend in two languages. If I could do both in one, that would be such a killer feature.
Clojure and ClojureScript let you do this (albeit in Clojure)