Post

Maynard
@quelklef.bsky.social

I got a partial understanding of inets from previous exploration but i feel like I'm failing to fully grok the intended denotation/semantics for any inet

aron
@adler.dev

yeah but arguably isn't that unavoidable? same way that if you got a randomly generated lambda calculus string its semantic meaning would also be inscrutable

aron
@adler.dev

lmao i love that you think i know more about this stuff than you do 😂

aron
@adler.dev

yes, but exactly for the purpose of trying to understand INs better!

aron
@adler.dev

that's actually the main reason why i made this, to have a way to get hands-on with INs so i can finally start to build some intuitions for them

Maynard
@quelklef.bsky.social

i am going to assume no so that i may continue talking. it's been a few years since I saw news about the project, but my recollection is that bend and HVM are (respectively) high- and low-level languages targeting inets as their model of computation

Maynard
@quelklef.bsky.social

afaik it's the passion project of one victor taelin, who felt that inets are both more beautiful and potentially more practical as compared to lambda calculus

lexi
@barredspirals.comint.su

the link routing algorithm is fantastic, every node editor needs to adopt it immediately imo. blender GNs would be so much less painful to read