off native dependencies, so let’s keep linking with it dynamically and, in development, just install it on our Ubuntu VM: $ apt-cache search '^libsqlite' libsqlite3-0 - SQLite 3 shared library libsqlite3-dev - SQLite 3 development files libsqlite3-mod-ceph - SQLite3 VFS for Ceph libsqlite3-mod-ceph-dev - SQLite3 VFS for Ceph (development files

16 bytes. Yup! I did a little lie just now. Let’s look at those values closer. Dynamic dispatch We’ll use LLDB to run through our program, setting a breakpoint right before the end of main: <i class="b fg-cyn">sansioex </i>on <i class="b fg-mag"> main </i><i class="b fg-red">[!] </i>via <i class="b fg-red">🦀 v1.83.0</i> <i class="b fg-grn

nits are just , candelas per square meter), and they’ve been tested to reach 413, so that’s cool. But that’s the absolute highest they’ll go. Right now I have them using the DCI-P3 color profile: A list of the color profiles available on my computer display, with DCI-P3 shown selected. And I have the “High Dynamic Range” option left

router ended up looking like: // this is a `ServerState` struct that has a cache, the config (including secrets) // stuff like that. we want that from any request handlers. let with_state = warp::any().map(move || server_state.clone()); // because most of my website is dynamic and rendered from liquid templates, // (and those

new style of dialogue, that’s more compact: It looks like this! I know! I made it! Lastly, I recently added support for KaTeX, so I can try and explain some maths: Of course, there’s no shortage of ideas on how to further improve the website: what about more dynamic content? What about fixing the reading time estimates? What about better

be? I feel like projects are always a lot more fun if they can hook into existing systems - just like the our ELF dynamic loader can run programs built with GCC, or how our userland ICMP implementation can ping real-world servers on the internet. So immediately my instinct told me this was a very dumb idea. But I like very dumb ideas! I figured at

enable-script=no --enable-ft=no --enable-fc=no --enable-ps=no --enable-pdf=no --enable-svg=no --enable-gobject=no --enable-trace=no --enable-interpreter=no --enable-png=no Basically, disable ALL the things. When all compiled, on Linux64, the dynamic libraries for cairo and pixman weighed about 11MB - a “ahAH! I was right! It was bad!” moment

Still, the cache status was “dynamic”, so every request went to the origin. I already had the cache-control header set for static assets (images, stylesheets, scripts), just not for HTML, because in two years of repeatedly hitting the front page of various sites, it was never a performance concern. Creating a page rule didn’t immediately fix

is not implemented for `[netinfo::IpForwardRow]` = note: to learn more, visit <https://doc.rust-lang.org/book/ch19-04-advanced-types.html#dynamically-sized-types-and-the-sized-trait> = note: required because it appears within the type `netinfo::IpForwardTable` = note: all local variables must have a statically known size = help: unsized

in draft), showing the first two paragraphs, and a Want to read more? box saying the box is Patreon-exclusive until some date, with an Add to calendar button and a Log in with Patreon button. The box goes on to explain that patrons of tiers Silver and above get early access to all posts The fundamental problems CDNs have with dynamic content like