Though I believe the core of his opinion hasn't changed so any video would tell you a similar thing or at least that's how I understood it. That LLMs, in the hands of an "expert", can enhance the way you work. Which is very different and a lot more realistic to what the current AI companies are saying(or were saying before they toned it down a bit for their IPOs).
> The web is a few dozen companies, each holding a filing cabinet, each with a receptionist posted out front. He'll read you one file at a time, but only files you can name, as fast as he cares to read, and as long as his boss allows.
Fortunately this isn't true. Social media consists of a few big walled gardens, but the web itself is still open. Go forth and create a website!
Yeah, but the web is getting smaller, as the most valuable and interesting parts got turned into private whatsapp groups or non-indexed discord and other "community first" nonsense, and went dark.
Yeah, I used to Google things until Google went to shit. Now I use Kagi, but it doesn't sound like a verb. I'll gladly add "search [it] up" to my lexicon :)
I learned about 0mq a few years back, found myself wondering why it had such an air of quality. Then I found Hitnjens' writing, only to learn that he had been gone for a while. I was surprised by my sense of loss.
Fwiw, not that it mattes a lot, I think most of that sense of quality in ZeroMQ is due to the very tasteful efforts of its main author, Martin Sustrik (https://www.250bpm.com/). Pieter Hintjens sortof stewarded the project but, I believe, didn't code all that much on it.
I did use the Xitami webserver in anger or years back in the early 2000s though, and that very much was Pieter's work! It was amazing!
I'm learning operating system fundamentals by writing baremetal code for my Raspberry Pi.
My medium term goal is to draw a cursor and move it using a mouse.
I recently got the USB host driver to the point where it could recognise port connects/disconnects. Enumerating USB devices involves some waiting, so I decided to work on concurrency support so that the USB driver wouldn't block the rest of the system. This week I got preemptively scheduled threads working (super fun stuff).
Now I'm trying to make the driver code more self-contained by keeping the driver's message queue on its stack. I'm not sure if it's a good idea. I'll play around with it for another day or two and then get back to USB enumeration.
I don't think v86 [1] is based on qemu, but it's a javascript (well javascript + rust->wasm) virtual PC. Not my project, it's super lovely for hobby os demos though. (And they've taken a couple of my PRs!)
> The commit activity might look unusual because I worked in very intense 12h/day sprints over 14 days.
That's a weird way to put it.
The commit activity looks unusual because it's a completed project whose files were individually committed in alphabetical order. There's no development history.
Most helpful references:
Intel Software Developer Manuals
for understanding x86 architecture
osdev.org wiki for the basics
(GDT, IDT, memory management)
Reading source code of other hobby
OS projects to understand different
approaches
James Molloy's kernel tutorial
helped me get started
Most memorable challenge:
Getting the window manager working
with proper overlapping windows and
mouse interaction. The z-ordering
and dirty rectangle system took me
a while to get right, windows kept
rendering behind each other or the
mouse would interact with the wrong
window. Debugging graphics issues
without a working debugger in your
own OS is... an experience haha.
Most surprising thing I learned:
How much modern OSes do that we
completely take for granted. Even
something simple like moving a
window smoothly requires double
buffering, proper
careful
memory management. Made me
appreciate every pixel on
my screen.
reply