4 ms·
The Esterel Language Primer: A Language for Reactive Systems (1999) [pdf]
- agumonkey 12y agoI remember being greatly confused Esterel it in college. Teachers didn't use 'Reactive' so I never thought about it that way, nor if it already had explored what the mainstream is rediscovering nowadays (Rx).
- seanmcdirmid 12y agoRx is not very comparable to Esterel, which is more about event-oriented programming than the classical meaning of "reactive" (today reactive somehow is taken to mean data flow but...that wasn't the case in the 80s).
- agumonkey 12y agops: Teachers used 'synchronous' as paradigm name (thanks to http://en.wikipedia.org/wiki/Esterel http://en.wikipedia.org/wiki/Esterel)
- pron 12y agoI posted this as an example of a language designed for verifiable correctness, predictable performance and a reactive design, and yet is completely imperative and full of side-effects. It is simply a demonstration that the pure-FP style is required (or even directly related) neither to verifiable correctness nor to reactive programming. The debate on the relative merits of various programming styles will continue, of course, but Esterel is an example that may contradict some notions that are a result of some fashions. Also, this categorization from Chapter 1 is interesting: Computerized systems can be divided into three broad categories: * Transformational systems compute output values from inputs values, and then stop. Most numerical computation programs, payroll programs, and compilers are transformational. * Interactive systems constantly interact with their environment in such a way that the computers can be viewed as the masters of the interaction. A user calls for services, the system listens to him when it can, and it delivers the services when they are available. Operating systems, centralized or distributed databases, and the Internet are interactive. * Reactive systems, also called reflex systems, continuously react to stimuli coming from their environment by sending back other stimuli. Contrarily to interactive systems, reactive systems are purely input-driven and they must react at a pace that is dictated by the environment. Process controllers or signal processors are typical reactive systems.
- seanmcdirmid 12y agoMy own research [1] goes in this direction: there is a lot to be said for control flow and spooky actions at a distance (I could never get the expressiveness I needed out of FRP). There is no one true paradigm. Esterel targets a low-level embedded domain where FSMs are sufficient and hard determinism is necessary. You might want to check out Francisco Sant’Anna's research [2], which is in a similar direction to Esterel but with Lua influences (same group in Brazil that does Lua, I think). [1] http://research.microsoft.com/en-us/people/smcdirm/managedtime.aspx http://research.microsoft.com/en-us/people/smcdirm/managedti... [2] http://ceu-lang.org/ http://ceu-lang.org/
- agumonkey 12y agoI remember seeing your page, but never noticed Jonathan Edwards being involved. I guess the editor is derived from his previous work on subtext.
- seanmcdirmid 12y agoHmm? No, the editor is all written in Glitch. Jonathan helped me write up the ideas and coined the term "managed time." We are also plotting world domination with new programming experience ideas (Athens, here I come!).
- agumonkey 12y agoI don't know it felt like sibling user interfaces somehow, but it's been a long time since I saw subtext1 presentation (http://imgur.com/uTXVg1V http://imgur.com/uTXVg1V), reading Edwards' name probably caused bias. Best of luck with your world domination plans.
- seanmcdirmid 12y agoWell, I am proud to admit that I steal a lot of ideas from Jonathan.