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.
> 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.
> Reading all the really, super old documentation that explains entire subsystems in amazingly technical depth
Any links?
> Maybe this is also why Smalltalk fiends are such fans.
I started getting interested in Smalltalk after I tried writing a MacOS program by calling the Objective-C runtime from Rust and had a surprisingly good time. A Smalltalk-style OO language feels like a better base layer for apps than C.
> do you think there's any appetite in people paying for this type of tool which lets you spin up infra on demand and gives you all the capabilities built so far?
(I'm not the author) The easiest way to charge for this kind of software is to make it SaaS, and I think that's pretty gross, especially for a CLI tool.
> I'm skeptical and I may just release it all as OSS
It doesn't have to be one or the other: you could sell the software under libre[1] terms, for example.
I often go one step futher by appending a short random identifier, `{service}.{id}@{domain}`, to make it harder to guess (in case someone learned of my email address policy).
I'm with you. Surprised by the negative reactions here.
A possible piece of the puzzle: I originally read the article on mobile, no issues. Then I opened it on my desktop, and found the design quite jarring. The margins are much too large for my taste, forcing the text into a single narrow column, and the header animations were distracting and disorienting (fortunately the page works perfectly with JavaScript disabled). Perhaps this triggered people?
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.