Plan 9 was intended to be Unix, done better. It preemptively replaced a lot of what we now bodge together with virtual machines, containers, and even microkernels, and it did it more simply and cleanly. But it wasn’t compatible enough to replace its ancestor. With off-the-shelf existing 21st century tech, we can fix that.

source: fosdem2024

It’s hard to believe, looking at the modern computing world, but there is still more to life than Windows or Unix… and today, most of the alternatives run on vanilla x86 hardware and are free.

Make something. Participate in something. Engage with someone. All of it might feel as unnatural as strapping on those running shoes after too long of a break, but once you’re back to creating, the energy comes by itself.

this collection of thoughts on software development gathered by grug brain developer

grug brain developer not so smart, but grug brain developer program many long year and learn some things although mostly still confused

source: dragonflydigest

There is something special in simple code. Here I’m not referring to simplicity to fight complexity or over engineering, but to simplicity per se, auto referential, without goals if not beauty, understandability and elegance.

Long ago, as the design of the Unix file system was being worked out, the entries . and .. appeared, to make navigation easier....

Architecture is hard sometimes--people keep offering up some new idea that quickly becomes the mainstream “way to do it” without any context or nuance, and the industry, desperate to find ways to improve their architecture, snaps it up without hesitation. Microservices was the latest in the trend, and it’s time we dissected the idea and got to the real root of what’s going on.

source: CaptainPatate

* Décongestion de réseaux
* Débuggage de logiciels
* Protection contre les virus
* Protection contre les tentatives d’intrusions
* Restructuration de services
* Partage de connexion Internet sans connexion
* Suppression aléatoire de compte utilisateur
* Protection anti-spoofing basée sur les adresses MAC
* Définition de politique de gestion et de sécurité aléatoire
* Elimination systématique des fichiers de log (journaux)
* Protection contre les DoS et DDoS grâce au système exclusif InUranus®
* Support de IPoT
* Rend vos données importantes accessibles à tout moment et à tout endroit
* Débloque les claviers qui se bl

source: CaptainPatate

source: https://tratt.net/laurie/blog/2023/how_big_should_a_programming_language_be.html

A curated list of openbsd’s innovations

Did Ken, Dennis, and Brian choose wrong with NUL-terminated text strings?

source: communications of the acm

In short, the argument goes, the ability to write scheduling policies in BPF greatly lowers the difficulty of experimenting with new approaches to scheduling. Both our workloads and the systems they run on have become much more complex since the completely fair scheduler was introduced; experimentation is needed to develop scheduling algorithms that are suited to current systems. The BPF scheduling class allows that experimentation in a safe manner without even needing to reboot the test machine. BPF-written schedulers can also improve performance for niche workloads that may not be worth supporting in the mainline kernel and are much easier to deploy to a large fleet of systems.

source: https://lwn.net

There are hackers—believe it or not—who just love the art of building software. They do it for the challenge, for the fun of it. They aren’t trying to make a million dollars.

Architecture is hard sometimes--people keep offering up some new idea that quickly becomes the mainstream “way to do it” without any context or nuance, and the industry, desperate to find ways to improve their architecture, snaps it up without hesitation. Microservices was the latest in the trend, and it’s time we dissected the idea and got to the real root of what’s going on.

In this article, we provide a holistic view of the Portable Operating System Interface (POSIX) abstractions by a systematic review of their historical evolution. We discuss some of the key factors that drove the evolution and identify the pitfalls that make them infeasible when building modern applications.

source: https://www.usenix.org