What a genuine read. And it is kinda the whole reason why i started blogging (shameless plug: stupid-ideas.com). You never git gud if you never start. And you innevitably look stupid to some people when starting.
This is why string instrument players sometimes prefer to play a note not on the empty string (let's say play a A on the A-string on a cello), but instead on a lower string (e.g. first finger, fourth position on the lower D string) to accord for these imperfections. As a string instrumemt player, you pretty much only have to worry about these notes on empty strings, every other note you can "wiggle into place".
However, by the fith axiom of euclid, the lines in your example cannot be parallel AND converge (not even in infinity). Thus, it's more an open rectangle.
Either they are overlapping which violates the definition of a triangle, or they don't and the parallel lines always maintain the same distance X to each other and consequently maintain distance X at infinity (let's say X=1, bc you can just scale it).
And rust doesn't market itself as small and simple scripting language?
Choose the tool that fits your usecase. You would never bring wasm unity to render a static html file. But if you make a browsergame, you might want to.
Ah, the good old squeak/smalltalk days. A few years back I worked on signals (or rather a static analyser for the editor to support signals) in squeak/smalltalk. The kind of signals those indie frameworks like angular and svelte now adopt trying to solve the problem of changepropagation you outline in your paper.
What i'm getting at is: For the places where other tools are better (like the UI example), we already have other tools (signals, observables, effects, runes,...). And for the places like client/server-communication: This is kind of where "call/return" usually shines.