The Linux Kernel Module Programming Guide (#LKMPG) got 5000+ stars on GitHub. Thank all the contributors and promoters. We are moving forward to Linux v6.x support. Rust LKM examples will appear later.
https://t.co/n8PKgCYxiO
In 1995, a small team of engineers unveiled a new programming language designed for flexibility, portability, and robustness. That language was Java. And three decades later, it remains one of the most influential technologies in the software world.
Thank you for helping us celebrate #30YearsOfJava this past year. We look forward to many, many more years of pushing the boundaries of innovation and the pursuit of developer excellence. ❤️
z386 is an open-source 80386-class FPGA CPU core that uses recovered Intel 386 microcode to run DOS and protected-mode software.
https://t.co/4qfPfjy0Vi
#OpenSource#i386
macOS is officially UNIX-certified because Apple pays The Open Group, runs the full compliance tests, and maintains it for each release. Linux isn’t, mainly due to high certification costs, extreme fragmentation across distros, and no real need since it’s already Unix-like enough for practically everything. It’s basically just a paid badge Apple cares about.
The Intel 386EX, running at 24 MHz, was a highly integrated embedded variant of the 80386SX architecture used in the Nokia 9000 Communicator, which supported internet connectivity via GSM circuit-switched dial-up data.
This is an interesting discussion, C is not Turing complete (if we are really pedantic).
The main issue is that in ISO C, the memory is finite, and bounded not just in practice but also in theory.
We can derive from these points from the standard (and a few more).
"Computer" once meant a human. Later, the term referred to machines, and humans became "programmers."
If programming also shifts to machines, what will human programmers be called next?
Before jumping into books like DDIA or Database Internals, it helps to understand the systems layer these designs are built on.
A lot of the design of such data-intensive systems is based on virtual memory: page tables, page faults, mmap, the page cache, swapping, NUMA placement, TLBs, and the tradeoffs between what the OS wants and what the database wants.
My latest article is a ~25,000-word mini-book on virtual memory.
It starts from first principles and goes all the way down to advanced topics like NUMA placement and performance debugging with tools like perf and /proc.
I also wrote it differently: as a dialogue between a user-space process and the kernel.
Most treatments of virtual memory are dry and fact-heavy. I wanted this one to feel more like a story, while still being technically deep.
Link below.