"Data can be an interface" is a pretty good and very underrated insight, I think.

Note that it's not just 'compilers' as an example of extremely complicated systems that achieve interoperability and componentisation by fully specifying and exposing data: *the Internet* does this too. At multiple layers: physical, data-link, TCP/IP, HTTP, REST.

It's almost like data is actually the best interface.

@natecull Yeah.

In FBP, or any data-flow programming, data is the only interface.

As for IRs in compilers specifically, is another example, and the name reflects how Racket in general operates, with layer upon layer of macros.
Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!