State of the SqueakPhone
syndicate-lang.org
syndicate-lang.org
(The phone side of things is exciting too, though as much as I like Smalltalk I wonder if Squeak is entirely up to the task of hosting a phone UI.)
Still need to dive further into the syndicated actor model side of things though; I think I have use cases for it but don’t entirely grok it yet.
- An essay on what the Syndicated Actor Model is: https://synit.org/book/syndicated-actor-model.html
- A big ol' glossary of relevant concepts: https://synit.org/book/glossary.html
- A protocol spec for interoperation among Syndicated programs: https://synit.org/book/protocol.html
Maybe some of these will be of use to you. I'm also happy to answer questions if you have any!
I worked with VisualWorks (nee Objectworks) for many years, and red/yellow/blue button events were still in the low level user input processing of code. They predated the semi-standardization of mouse buttons. I still have a strong synaptic response for them. My brain just automatically knows what kind of operations it will find for each of those colors.
If anyone wants to really understand what's going on, I'd recommend looking at preserves[0], a serialization format Tony and some others have been working on. Preserves is a superset of JSON with actual semantics, a schema language and a binary representation. Syndicate, syndicate-server and synit all follow protocols defined in preserves schema, and so those are a good hook into learning how this system works.
Synit itself is impressive. With nearly trivial effort, I was able to get a web server running as a daemon, and verified that it was resilient to my repeated `killall`s.[1] I simply replaced the `"echo httpd"` with `"python -m http.server"` and then started `syndicate-server -c ./boot` inside the `experiments/layered-server-config/` directory. This example is actually overkill for my use case (a replacement for supervisord), but is simple enough that it can show how Synit works without much clutter.
Congratulations, Tony!
[1] https://git.syndicate-lang.org/synit/synit/src/branch/main/e...
Smalltalk projects like this (and Pharo) are the only things keeping me interested in OOP and hesitating to go all in on FP.
Because that's the main thing I am looking for in a smartphone.
Seriously though, is "not being systemd" such a strong part of the project's identity that it bears being repeated so much?
The systemd people have managed to get their project in as the default on many distributions. They have no excuse for having a thin skin about being labelled as the default which will be replaced.