I guess you could do double-speed, but I find that somehow stressful.
Edit: I just read the paper. It took me 21 minutes. It's not long, only 11 pages.
Slight spoiler: they have lots of criticisms of the paper.
Also, show notes link to the paper that they talk about that they do like much better.
This format isn't inefficient, you're just judging it based having a different goal than it does.
Finally the are useful for synthesis…a podcast can talk about tenuously related topics that would not usually be appropriate for an academic paper; use analogies, metaphors, and similes; and simply go off topic and discuss other interesting ideas that turn out to be more applicable than the formal subject.
But again that’s for me, not someone else.
If I listen to a podcast I want to learn something, gain a new perspective, listen to a well-moderated conversation or at least laugh.
This podcast does none of those things. Literally doing nothing and letting my thoughts wander is more interesting than listening to this.
Like, it's a basically blogpost that muses about uhhh couple examples it pulled at random from esolang wiki and has literally no point. Beside prescriptive one. Formatted as a paper, which I admit takes some skills.
Ex: my car's heater doesn't work the moment you turn it on. So if I enter the car one of my first tasks is to turn the blower down to 0 until the motor warms up. A learning language could be used here, given free reign over all the (non-safety-critical) controls, and told that it's job is to minimize the number of "corrections" made by the user. Eventually it's reward would be gained by initializing the fan blower to 0, but it might take 100 cycles to learn this. Rather that train it on a GPU, a language could express the reward and allow it to learn over time, even though it's output would be "wrong" quite often.
That's an esoteric language I'd like to see.
I was about to suggest probabilistic programming, e.g., PyMC [3], as well, but it looks like you want the optimization to occur autonomously after you've specified the problem - which is different from the program drawing insights from organically accumulated data.
[1] https://github.com/Z3Prover/z3?tab=readme-ov-file
[2] https://microsoft.github.io/z3guide/programming/Z3%20Python%...
> One of the biggest goals of this show — our raisin detour, if you will...
brudgers•4mo ago