Everything live/reactive about tablam HOT 4 CLOSED

Not likely. The exact shape of the parallel/async support is not yet defined.

from tablam.

Fundamentally this has nothing to do with async/parallelism (even though paralellelism and/or async stuff is one of the ways to implement this).

So my question stands 😉.

Else how would you want to achieve data-orientation if a change to a cell/value will not propagate to readers?

from tablam.

even though paralellelism and/or async stuff is one of the ways to implement this

Yeah, sure!.

I'm looking for a small set of common paradigms that could solve several use-cases, so any chance of this need to be on top of that...

Else how would you want to achieve data-orientation if a change to a cell/value will not propagate to readers?

That is a kind of data orientation, alike was with http://witheve.com. Having some support for this could be neat (a better way to do "triggers"), but I think that will be among the lines of have an actor system or channels like in go, instead of something fundamental to the lang.

P.D: In https://www.reddit.com/r/ProgrammingLanguages/ is a good place to get a better response about deep stuff like this. I'm open to ideas, as I said, not yet settled on how exactly to deal with the fundamental task of making operations concurrent/parallel, and I'm looking for something relatively easy to implement AND for the end-user to understand.

from tablam.

Ah, ok. I see you are not convinced that such kind of "liveliness/reactiveness" belongs to the "small set of common paradigms" to build upon.

And that is OK (despite me being convinced it is the other way around 😉).

(feel free to ping me to discuss async/parallelism/concurrency/reactiveness/you_name_it as I have spent already too many years with this topic as you can see e.g. on GitHub in hundreds of discussions in different projects 😉)

from tablam.