Ticklet has state. Function does not have state.
Observer pattern suffers of threading symptoms described in Program flow.
Ticklets are completely opposite concept that threads.
|implicitly parallel||explicitly parallel|
|explicitly sequential||implicitly sequential|
See Program flow for main difference between threads and ticklets.
Only important relation between threads and Tickator is, that current implementation uses threads. That will be removed once there will be CPU that will execute ticklets natively.
Tickator is inspired by digital circuits. See Architecture. Tickator may however differ in aspects that are not doable on wire level. For example it is possible to connect multiple outputs to single input. That is not doable on hardware level.
VHDL is used for programming digital circuits and Tickator is inspired by digital circuits. So Tickator is similar to VHDL. But just a little bit. Tickator is abstracted from physical hardware so there are no hardware limitations:
Also, Tickator is supposed to be generic programming tool. VHDL is typically used just for hardware and FPGA programming.
Tickator uses global tick on smallest possible granularity. In best case there are thousands of small processors that sychronizes at each instruction by global tick.
Games and simulations ticks on high levels - one frame or simulation cycle. In between them they behaves as normal software.