#42

don’t you have to do that in FRP as well? a declared handler still has to know what to do. but if i understand correctly it makes it easy to declare new events, so instead of a general handler that has to maintain the overall state of UI you can have handlers be closer to the events they should be reacting to and knowing only the minimal scope they need to know. but you could implement it in a procedural language as well. but yeah, it’s nice to have the language itself provide some scaffolding (it feels like C# has been trying to employ some FRP techniques as well…)

1 Like
#43

:slight_smile: this is fantastic!

it’s so cool (feeling grateful) to be looking in
on this professional level
programing theory discussion/seminar, please continue…

'the poetry of code

it makes me think of this (l.wittgenstein)
and this (reggio emilia poem)
everything is a language

computer programmers get to define/accept the definition(s) of a language
and can expect the computer to execute the code exactly the same way, every time
(it’s from brazil, is there a portuguese flavor of Lua?
is it slightly different in angola?)

spoken languages develop culturally over time
music shows happen in a cultural context
even in the same language (english, say)
america, england, new zealand
words/musical constructs, have slightly different meanings/connotations

music is a language
performance is a language
I’ll start another thread :slight_smile:

2 Likes
#44

This seems relevant to our interests:

1 Like
#45

Bumping this topic because I feel a lot of the issues that were discussed here remain relevant now that norns is approaching 2.0.

It might be useful to focus on the use cases that @mzero mentions here: