Announcing an operator lookup tool for OCaml! ๐ซ
๐ https://t.co/U7etlhS63Y
It takes an OCaml operator or syntax element and gives an explanation of its behaviour, usage examples and warnings about common misuses.
Thanks to @JoshWComeau for the idea and design elements.
[private message on work slack]
friend: hey buddy how do i <do thing>, i can't find it in your team's docs and i feel super dumb
me: hey buddy! it doesn't exist. please re-ask this question in our public help channel so whoever is on-call can answer you.
[public help channel]
friend: hi team, our service needs to <do thing> because of <legit reasons>. we're wondering what the right way to do it is. thanks!
me (also the on-call): hello, this is not possible at the moment, but we'll add a ticket for it and prioritize it in our upcoming sprint.
ah yes, increasing the speed of an OCaml program by up to 50% by predicting memory allocation patterns.
The correctness is straightforward, but why is it faster ?
When unrolled i get a 2x improvement over the naive loop.
Would love a Terraform provider for MacOS system preferences โ bit fed up slowly re-creating the same config on each machine I ever use / reconciling drift manually.
A sweet example of #offlinefirst application built using #Irmin and #OCaml. Backup your browser application data in Git on the server-side and use a 3-way merge strategy to reconcile any conflicts. Great work @dinakajoy !
Finally got around to fixing the initial dark mode flicker on my site ๐ Only took me several years to get around to it...
Dark mode + SSR always feels more complicated than it really should โ props to @JoshWComeau for his excellent post on the subject. https://t.co/dI6WuHE52z
Caching aside, I thought there would be more paranoid/risk-averse consumers of popular base images (distros) reproducing image hashes themselves (in multiple places / by multiple engineers), but looks like 99.99% just delegate trust to the vendor via signing & leave it at that.
Surprised that relatively few folks seem interested in having their Docker images be truly "reproducible" (in the byte-for-byte sense, not just a fuzzy notion of equivalent output).
There seems to be plenty of ways to do it, but none of them seem to be used _that_ widely.
@TheEduardoRFS Probably a lack of pre-provided editor tooling making this feel more heavyweight than it actually is.
Should be able to jump quickly between corresponding definitions, or generate them on-demand by inference if they don't already exist.