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.

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

This is an attempt to stop a war. I hope it is not too late and that somehow, magically perhaps, peace will prevail again.

The latecomers into the arena believe that the issue is: “What is the proper byte order in messages?”.

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

source: communications of the acm

* 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

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

source: unixsheikh

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.

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

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.

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

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

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

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.

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

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

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

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