Erlang has the right concurrency model, but the language is not object-oriented.
Python has a great object language but only a single thread at a time.
Go is statically bound. Which brought me back to my beloved Objective-C.
But what to do about concurrency? I found the answer right here. Thank you very much.
I would have sent you a more private email message, but could not find one.
I am quite surprised that this repository has not been updated since 2015. Maybe the problem is that
you have to create a new class for every message. Have you considered Mulle Objc. https://github.com/mulle-objc
Rather than passing arguments on the stack, their messenger treats every message as a data structure.
So no need to create custom messages. So this approach would work great.
I am happy to talk more in person.
You can reach me at PythonLinks.info/contact
Warm Regards
Christopher Lozinski
Thanks a lot for the kind words @PythonLinks! And sorry for the massive reply!
In all honesty, this project was merely an experiment/showcase I did back in 2013.
Checking out your link to mulle-objc now 🙏
I am trying to build a real time server.
Erlang has the right concurrency model, but the language is not object-oriented. Python has a great object language but only a single thread at a time.
Go is statically bound. Which brought me back to my beloved Objective-C. But what to do about concurrency? I found the answer right here. Thank you very much.
I would have sent you a more private email message, but could not find one. I am quite surprised that this repository has not been updated since 2015. Maybe the problem is that you have to create a new class for every message. Have you considered Mulle Objc.
https://github.com/mulle-objc Rather than passing arguments on the stack, their messenger treats every message as a data structure. So no need to create custom messages. So this approach would work great. I am happy to talk more in person.
You can reach me at PythonLinks.info/contact Warm Regards Christopher Lozinski