https://lwn.net/SubscriberLink/905164/8c13fabaff641359/ · Docker and other container engines can greatly simplify many aspects of deploying a server-side application, but numerous applications consist of more than one container. Managing a group of containers only gets harder as additional applications and services are deployed; this has led to the development of a class of tools called container orchestrators. The best-known of these by far is Kubernetes; the history of container orchestration can be divided into what came before it and what came after.
https://github.com/canselcik/libremarkable · The only public framework for developing applications with native refresh support for Remarkable Tablet - GitHub - canselcik/libremarkable: The only public framework for developing applications wit...
https://cmdk.paco.me/ · Fast, composable, unstyled command menu for React.
https://v5.chriskrycho.com/journal/some-thoughts-on-zig/ · One of the biggest things Zig has going for it—especially compared to Rust—is that it is (relatively) small. That sits in tension with Rust’s approach to solving memory safety problems, and sets up a nice challenge for future programming language designers.
https://recursion.wtf/posts/rust_schemes/ · This is a post about writing elegant and performant recursive algorithms in Rust. It makes heavy use of a pattern from Haskell called recursion schemes, but you don’t need to know anything about …
https://ariadne.space/2022/07/17/how-efficient-can-cat1-be/ · There have been a few initiatives in recent years to implement a new userspace base system for Linux distributions as an alternative to the GNU coreutils and BusyBox. Recently, one of the authors of one of these proposed implementations made the pitch in a few IRC channels that her cat implementation, which was derived from OpenBSD’s implementation, was the most efficient.
https://www.thecodedmessage.com/posts/2022-07-14-programming-unwrap/ · UPDATE 2: I have made the title longer because people seem to be insisting on misunderstanding me, giving examples where the only reasonable thing to do is to escalate an Err into a panic. Indeed, such situations exist. I am not advocating for panic-free code. I am advocating that expect should be used for those functions, and if a function is particularly prone to being called like that (e.g. Mutex::lock or regex compilation), there should be a panicking version.