Regarding the thesis of the article of bringing the instructions to the data, I'd love to see the core of that applied much more broadly in software / aaSes. Random services probably won't JIT LLVM IR for you, given the security of running untrusted LLVM IR … but there's also WASM out there. I'd <i>love</i> to see interfaces start having the capability of accepting WASM instead of an enumeration of the 2 use cases a PM thought I might have.<p>E.g., we use PagerDuty, and there's several places, such as routing pages, where I'd just like programmatic control, and <i>code</i> would express much more succinctly the needs of what I want to do than trying to express it through some UI-based "routing" editor thing.<p>Artifact storage aaS's often come with "cleanup" policies that let you choose between 2-3 different modes of cleanup, mostly wrong one way or another.<p>In all cases an enumeration of the names of 2-3 fixed functions, when I'd rather <i>pass the function</i>.<p>---<p>Since this is posted by the author… you set `.content a { word-break: break-all; }`? Like the name sort of implies, it permits line breaks <i>anywhere</i>, which means that the opening line renders as,<p><pre><code> One paper that has been in the back of my mind is for a few years is Efficiently Compil
ing Efficient Query Plans for Modern Hardware1 which details how Tableau's internal
</code></pre>
(I.e., it splits mid-syllable, and without a hyphenation (which is a different CSS property).)<p>The layout is basically fixed at the containing element's max-width for nearly any width someone might reasonably be using, so outside of font variations, it should basically always render like that (and I don't think font variations would make enough of a difference). (It steps up to a wider width at some point … but that width <i>also</i> lops a word on the opening line.)