But hell yeah: it is possible to do VERY efficient, typed, comms languages, and building in autodiscovery is like having mdns+openapi, which you can use to make very very neat cli + gui tools.

I really want to make things like old smalltalk system browser for network services.

Re: jyn.dev/the-terminal...

I would love to chat about the stuff I'm doing with postcard-rpc/ergot but also poststation: I'm building a typed, autodiscoverable, lightweight socket library that I'm using as a network transport library but also I want to make it my hobby os' syscall/ipc interface

It's all those 512MiB u8 arrays you leave lying around everywhere

Ooh, I'll check! I'm probably back a couple of point releases

it usually gets awkward on exactly how far that "is a" goes, especially if the definition of that is more implicit/abstract.

Or maybe I've just smashed composition into my head hard enough that OO just feels weird now.

The way I usually teach this for traits (esp embedded-hal) is that there's three things:

* The definition of the interface
* The provider of the interface
* The consumer of the interface

I think in less abstract sense the provider is also implicitly the definer, but when it comes to more OO "is a"

Probably tens of millions in actual spending (staff, contracting, foundation contributions), but probably hundreds to thousands of engineer years of pure volunteer work

(to be clear, I'm probably more mad at capitalism than AI here, but what are you gunna do)

my favorite part of systems engineering is that people and organizations are systems too, and you need the same kind (or at least for me, an appreciably similar kind) of mechanical sympathy for human systems, to help understand, diagnose, and improve (or at least optimize for an outcome).

aww they're just little guys

ergot has type punning and manual vtables too :)

You could code review ergot (and cfg-noodle) :D