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

The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed does not mean you should stop others from building one just because you do not like the color they plan to paint it. This is a metaphor indicating that you need not argue about every little feature just because you know enough to do so. Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change.

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

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

People who know what they are doing run FreeBSD! Everyone in the communication industry run FreeBSD!

source: unixsheikh

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.

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

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

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.

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.

A curated list of openbsd’s innovations

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

a. Learn to learn
b. Learn to question things
c. Acquire the permanent habit of learning

source: queue.acm.org

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

source: dragonflydigest

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

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

What happens inside the cpu? how things get delayed...