Whole-known-network
<p><span class="h-card" translate="no"><a href="https://chaos.social/@jacqueline" class="u-url mention">@<span>jacqueline</span></a></span> ive filled this in with my imagination adn now im mad at oyu</p>
<p>we had two ideas but they were both a little bit too spicy, so u just get a shitpost sorry</p>
<p>hot take</p>
<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@jevanko" class="u-url mention">@<span>jevanko</span></a></span> nice to hear. from my experience, I'd try to avoid functorizing everything - with the rule "use a functor if you need this data structure multiple times with different types in a single application" (i.e. Set.t, Map.t) -- but even that you can avoid, see Hashtbl.t. :)</p>
<p>Talk #12: "Programming Without Pointers" by Andrew Kelley (<span class="h-card" translate="no"><a href="https://mastodon.social/@andrewrk" class="u-url mention">@<span>andrewrk</span></a></span>)</p>
<p>Lightning talk #4: "Reliable Serverless Needs Distributed Transactions" by Stu Hood</p>
<p>Talk #11: "A Polymorphic Data Model for SQL using Algebraic Types" by Steve McCanne</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://digipres.club/@foone" class="u-url mention">@<span>foone</span></a></span> <br />Maybe, but ignoring exceptions doesn't feel pythonic</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> Backwards compatibility is very important and should be included in at least a generation or more of consoles.</p>