29 points bhaprayan 19 hours ago 5 comments
Sharing a thought experiment I put together. The premise: what might declarative programming feel like for the physical world?
We’re already familiar with this paradigm in software land (eg SQL etc where we declare what we want and the execution engine figures out how).
I didn’t have access to an actuator so I mocked up the concept in software. The way it works is you demonstrate the effect and the system figures out how to achieve it. So say you want to ring a bell and you have a crank. The system will find a way to connect the two. If you add obstacles it figures out how to work around them (runs a constraint solver runs behind the scenes).
I think what’s interesting about this is being able to think about the problem at a higher level of abstraction, with the system figuring out a way to achieve the intended effect.
Anyways, curious to read reactions, feedback, and interesting ideas on how to extend this!
skinfaxi 32 minutes ago | parent
bhaprayan 23 minutes ago | parent
Behind the scenes, I’ve tried to make the audio production realistic, so there’s some acoustic modeling going on (eg echoes, attenuation of sound, etc). But yes you could imagine having the input forces be continuous and having the mechanism trying to figure out how to reproduce the sound exactly.
jdw64 22 minutes ago | parent
[1]https://www.microsoft.com/en-us/research/publication/motion-...
bhaprayan 7 minutes ago | parent