Reactors are currently local: https://doc.red-lang.org/en/reactivity.html
How to scale and distribute them is a great thought experiment, which will also depend on the actor/concurrency model. I like the idea of reactive tuplespaces myself.
parsefor matching, so rules can be arbitrarily complex.
Different beasts indeed. And whether Eve will succeed is not a given. Spreadsheets are a huge win, because they're easy to reason about, especially if you're familiar with the domain. Eve needs to magically produce expected results for non-programmers in the same way, from a simple UI. Otherwise Prolog would have won long ago.
Red isn't meant for non-programmers. However, programmers come in shades of gray. Red is very accessible to casual programmers, as BASIC and VB have been. And also, though we have some thought to apply in the presentation, like Logo. What Red promises, in one narrow view, is the ability for each level of competency in programming to build tools and share with other levels, without resorting to different languages.
series!and how to deal with it (I'm looking at you
copy), what's a
word!, what's a context, bindology, etc.
I used r-b-e a few times before I discovered
what function ;)
For those new to Red, does confusion come from:
- Trying to understand how Red works internally?
- Mapping what you know of other langs to Red concepts? i.e. it doesn't "work like X".
- Red not doing what you expect?
- Something else.
Does red-by-example.org help?
@greggirwin , Red-by-example does help quite a bit. It would be cool if it was a bit more complete.