libxev — libxev is a cross-platform, high-performance event loop that provides abstractions for non-blocking IO, timers, events, and more and works on Linux (io_uring or epoll), macOS (kqueue), and W…
The subject this post names, from the same vocabulary
the directory files beliefs under, and the words it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
At some point, the Linux press has to stop treating it as news that some weirdo who got comped a $50 droplet is mad about DigitalOcean donating $3m to the Omacom Foundation.
More and more of our personal and professional computing experiences will come from agents that orchestrate work in the cloud, using sandboxes. Those sandboxes will be Linux.
The case for *total* Linux victory (desktop, mobile, server, iot, robots, embedded…): 1) Most agent-programmable People will want fully personalized computing experiences.
Linux conquered everything else. All the AI infrastructure that everyone runs off, it's all running on Linux. All the systems, all the servers, everything is Linux. So it was kind of a curiosity that the desktop and the personal computers we were using really hadn't been captured, but clearly it was just waiting for this moment. Linux spent the time from '91 to now waiting for agents to fully flourish as an end user operating system.
It is an infuriatingly locked-down computer. Now, to Apple's credit, it's a pretty good computer for being locked down, but I don't want a locked-down computer. I wanna own my computer. Better yet, I wanna mutate my computer, and this is where the agentic age needs a new operating system. When you can vibe code whatever app comes to your mind, you should be able to vibe code your operating system.
I don't require anyone to be as excited about AI or agents as I am. It's completely fine. But we also need someone in this camp in this Linux camp who are really excited about AI, who really leaning in with agents.
Preventing companies from building data centers in America wouldn't slow down the rate of progress in AI. It would merely slow down the rate of progress in AI in America.
And it's effectively the next step of, you know, every phase of of software evolution is just like a rising tide of abstractions. This is the next abstraction.
Nicely written and an entertaining story of Linus Torvalds and the creation of Linux kernel. I read it in high school and it definitely strengthened my interest in computer programming.
Smalltalk Best Practice Patterns. True, Kent Beck is better known for his later work, which is excellent too. But Smalltalk Best Practice Patterns is particularly strong on coding style. I learned a lot by just reading the code examples. Small tweaks to names and abstractions add up. No one captures that better than Kent.
I would say here that the Linux kernel is truly unique in this particular aspect in that they have thousands of contributors doing it on work time. I actually think that the Rust project is doing pretty well at having people do it and get paid for it like by their employer, but it's nowhere near the to the same extent as as the Linux kernel.
The big news were that at the Linux kernel maintainer summit, we agreed that Rust is no longer experimental in the kernel. That was really big for us compared to the previous year.
Another thing that's really cool is you can contribute to the Linux kernel without contributing to the Linux kernel, right? because you might take a Rust language feature we need and implement it and now you've contributed to the Linux kernel indirectly
I think where Rust is really unique is in the combination of things. So on one hand, it it doesn't have a garbage collector and it it's usable in low-level context like the Linux kernel or firmware or whatever.
But I have come to realize that as a web developer, Linux is just better. Linux is just better. It's closer to what I deploy on. The tooling is actually phenomenal.
Their words now
anyone who's working with the web, who's working with Ruby, who's doing DevOps, they should be on Linux because first of all, that's closer to what we deploy.
So the question is how do I refactor all the abstractions so that I'm not I have to arrange it once and hit go. The name of the game is how can you get more agents running for longer periods of time without your involvement doing stuff on your behalf?
The Moonlight client is available for virtually every platform: Mac, iOS, Android, and of course Linux. That means no need to dual boot to enjoy the best games at the highest fidelity.
Use red and amber lights in the evening . Bluelight is bad for sleep. You can get blue light blocking apps (f.lux), glasses and also turn red mode on your phone.
I'm getting into screen-time blocking. I use the app Opal on a recommendation from Lucas Gelfond. It won't let me scroll Twitter, Substack, or Instagram for 80% of the day. Gmail is also blocked from 11pm to 8am.
It's becoming much more a thing of the past. So I think you just have to be adaptable and flexible. I think people will have to get skills that are transferable, like learning one specific programing language or one specific subject of mathematics or something. That itself is not a super transferable skill, but sort of knowing how to reason with abstract concepts or how to problem solve when things go wrong.
This is getting easier in the lastest versions of Fedora and Ubuntu (e.g., Ubuntu 24.04 LTS) which are shipping system libraries with frame pointers by default.
Beyond the Visible: Hilma af Klint (Germany, 2019, CC) 3.6 When thinking about the most overlooked female artist, Artemesia Gentileschi often comes to mind. This documentary makes a persuasive case for Hilma af Klint. To my eyes, her most appealing works are not the large scale abstractions, rather it’s the small Klee-like gems that stand out. Don’t assume that if you have seen a half dozen of her most famous works that you have any conception of her overall career.
The Linux Programming Interface by Michael Kerrisk – an exhaustive reference on how Linux works. There are about a million chapters, but every individual chapter is pretty short and I find it quite readable.
Programming, of course, is forgetting, but we need to at least try to be aware of the costs of the abstractions we choose and consider who it is that ends up being forgotten.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.