Live data from Hacker News

Proto Actor – Fast distributed actors for Golang and C#

proto.actor

41–47 of 47 posts

Re: Proto Actor – Fast distributed actors for Golang and C#

#41
post #40
post #37

Earlier quoted context omitted.

What is the difference between multithread and different machines? Time to get a synchronous response ? At best. But errors happens to and error situations are the same.

But why are types a problem?

Because typing errors and infinite timeout is really hard..

Re: Proto Actor – Fast distributed actors for Golang and C#

#44
post #43
post #42

Earlier quoted context omitted.

I can't understand this. Can you give a more concrete example?

How do you prove something that is undecidable ?

Look, I honestly don't understand what you are talking about. Why suddenly we are talking about undecidable?

I have not experience in this area.

Re: Proto Actor – Fast distributed actors for Golang and C#

#45
post #44
post #43

Earlier quoted context omitted.

How do you prove something that is undecidable ?

Look, I honestly don't understand what you are talking about. Why suddenly we are talking about undecidable? I have not experience in this area.

If something have an infinite timeout, how can you know it will be the correct type that come back, because you can not know what comes back.

Re: Proto Actor – Fast distributed actors for Golang and C#

#46
post #45
post #44

Earlier quoted context omitted.

Look, I honestly don't understand what you are talking about. Why suddenly we are talking about undecidable? I have not experience in this area.

If something have an infinite timeout, how can you know it will be the correct type that come back, because you can not know what comes back.

Ok, but is the same problem if is untyped, or you mean that while program A is waiting for B to return [String], program B is updated to return [Int]?

But is the same if untyped. Because the internal schema is changed?

Re: Proto Actor – Fast distributed actors for Golang and C#

#47
post #46
post #45

Earlier quoted context omitted.

If something have an infinite timeout, how can you know it will be the correct type that come back, because you can not know what comes back.

Ok, but is the same problem if is untyped, or you mean that while program A is waiting for B to return [String], program B is updated to return [Int]? But is the same if untyped. Because the internal schema is changed?

what is the usage of your type if you can not check them through the compiler ?
Post reply on HN