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

Simplicity is the heart of the Unix philosophy. The more code lines you have removed, the more progress you have made. As the number of lines of code in your software shrinks, the more skilled you have become and the less your software sucks.

With the “Web Development Manifesto” we strive to maintain minimalism and clarity to drive web development to a completion that result in a much more sane World Wide Web.

source: https://unixsheikh.com

Adoring admirers have fed Linux goodies to a disheartening state of obesity.
If only some reincarnation with the genius and sensibility of Ken Thompson and Dennis Ritchie were still guiding the evolution of Unix!

source: https://www.wikiwand.com/en/Unix_philosophy

Monolith vs microservices ... small server vs big server...

We have all gotten so familiar with virtualization and abstractions between our software and the servers that run it. These days, “serverless” computing is all the rage, and even “bare metal” is a class of virtual machine. However, every piece of software runs on a server. Since we now live in a world of virtualization, most of these servers are a lot bigger and a lot cheaper than we actually think.

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

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

A curated list of openbsd’s innovations

* 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: dragonflydigest

Think about all the things they’ve told you that you 𝑛𝑒𝑒𝑑. HTML is NOT the answer!

source: https://hackers.town/@lmorchard/109444911452419131

Paul Baran (born Pesach Baran /ˈbærən/; April 29, 1926 – March 26, 2011) was a Polish-American engineer who was a pioneer in the development of computer networks. He was one of the two independent inventors of packet switching.

source: book; where wizards stay up late

Writing is key to have impact in large organizations. As a senior software engineer chances are that writing is the most important skill you have to acquire in order to increase your scope beyond the team and advance your career.

This article contains some learnings that have helped the author to become better and more productive as a writer over the past 15 years.

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.

source: queue.acm.org

Lawrence Gilman Roberts (December 21, 1937 – December 26, 2018) was an American engineer...

As a program manager and later office director at the Advanced Research Projects Agency, Roberts and his team created the ARPANET using packet switching techniques invented by British computer scientist Donald Davies and American Paul Baran.

source: book; where wizards stay up late

Joseph Carl Robnett Licklider (/ˈlɪklaɪdər/; March 11, 1915 – June 26, 1990), known simply as J. C. R. or “Lick”, was an American psychologist[2] and computer scientist .... He is particularly remembered for being one of the first to foresee modern-style interactive computing and its application to all manner of activities; and also as an Internet pioneer with an early vision of a worldwide computer network long before it was built

source: book; where wizards stay up late

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

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