I read the article you referenced. It's based on, and described wrt, Python's `async with` (so quite a few layers of abstraction), so I can't say with certainty how it's implemented. But, as I noted earlier, it isn't really that different from a run-till-completion task scheduler and is not particularly novel or interesting, imo.
The point I was trying to make is that you can apply the actor model to any system of isolated processes. Whether the isolated processes live on a distributed system of networked computers or on the same computer is an implementation detail. The critical issue is that each actor should own and mutate its own state. Whether all actors run on the same thread or on separate threads is also an implementation detail. For instance, AtomVM is a lightweight implementation of the Beam (actor model) that runs on microcontrollers [0].
> The entire thrust of this thread is that you can have a more reliable system that is easier to reason about if you use specific constructs that each have less power
Easier to reason about, sure, fine. Your earlier comment claims the actor model is a dead end in non-distributed systems.
> Unstructured concurrency should be reserved exclusively for contexts where structured concurrency is impossible, which is what the actor model is for.
Results from my quick search on structured/unstructured concurrency were all references to Swift. Is this a Swift thing? In any case, the issue appears to be more about managing tasks that don't require a preemptive scheduler. As I see it, that issue appears orthogonal to distributed/non-distributed systems.
Nurseries sound similar to run-till-completion schedulers [0].
> IMO the urge to use both the actor model (and its relative, CSP) in non-distributed systems solely in order to achieve concurrency has been a massive boondoggle
Can't you model any concurrent non-distributed system as a concurrent distributed system?
There's limited coverage of all global conflicts, certainly in American media, but quite likely in other Western media.
> What explains the silence from activists outside Iran on this particular issue?
What explains the silence from the media on all other conflicts. It's certainly not because lives are not being destroyed in Sudan [1] and Myanmar [2].
> The people who pay into this are either taken in by the pretense that they’re sponsoring open-source work
> Honestly, I think the first category is somewhere between "microscopic" and "nonexistent", but most people in the second category will end up holding the bag when this thing inevitably collapses.
I agree. There may be folks willing to support open-source software via a crypto-friendly vehicle, but most involved in this are hoping to make money on a pump and not get left holding the bag.
Everyone involved in this scheme is fully aware of the game being played (or should be) and the risks involved. The notion that "crypto grifters" are corrupting naive open-source developers just strikes me as an odd way to describe such activity.
As an engineer, I can confirm that this AI (if it works well) would compress the prototyping stage significantly, resulting in a better product at reduced cost.
> also coming up with the plausible load paths and deciding on the geometry of the parts according to the actual loads
Do you have a brand you'd recommend?