Programmer's critique of missing structure of operating systems
I think the browser is the described OS here: every-api passes objects around, IndexDB is your filesystem, remote REST &amp; GraphQL servers are returning structured JSON objects to your program, you can add a &lt;script&gt; tag to your &lt;html&gt; to pull in your single-function scripts (i.e. leftpad).<p>Seriously though, the question of &quot;why isn&#x27;t it done this way&quot; is answered a couple times: &quot;it&#x27;s all just bytes in the end&quot;. Bytes &amp; arrays-of-bytes are really the only thing that you can trust that all systems and all languages interpret the same (even 2-byte integers can be interpreted differently by different systems). Presumably the author just wants to be able to memcpy structures between programs or from disk, or maybe with some high efficiency pre-allocated heap stuff, but you really need to have code to validate the bytes, essentially requiring the parsing of your data-structure which the author is trying to avoid.<p>Running programs with some common argument notation does sound really nice, but ideally that&#x27;s just calling a function from your language&#x27;s binding to their library (as their executable should do, right?).