Why We Replaced Firecracker with QEMU | Hocus Blog
In the early days computers were much simpler. The var-ious components of a system, such as the CPU, memory, mass storage, and network interfaces, were developed to-gether and, as a result, were quite balanced in their per-formance. For example, the memory and network inter-faces were not (much) faster than the CPU at providing data
Ulrich Drepper • File
As Fred Brooks pointed out almost 50 years ago, “adding more engineers to an already late project won’t make it go faster”.
sharedphysics.com • When Everything is Important But Nothing is Getting Done
Perhaps surprisingly, virtually all of decentralized finance, aka DeFi, consists of finite state applications. As long as you can store a handful of account balances, you can start to build arbitrarily-complex tools for people to trade, borrow, lend, etc... and you'll never have to store more than the ending balances in the long-term. This is becau... See more
Deso • Web3 Will Not Be Built on Smart Contracts • DeSo (Decentralized Social) Blockchain
What Every Programmer Should Know About Memory
The document discusses the structure and limitations of memory subsystems in modern commodity hardware, with a focus on CPU caches and how programmers can optimize memory access for performance.
people.freebsd.org