> 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.
> 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.
Generally everything in that documentation archive is absolutely amazing. I don't know why it's an archive; presumably they laid off or reassigned the entire team working on it and there will be no more. The closest thing today would probably be Technotes: https://developer.apple.com/documentation/technotes
> 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.
Agreed that SaaS feels ugly. Agreed on selling it as libre. The only thing I could imagine charging for in a subscribed model would be for services that are hosted (e.g. instance/gpu provisioning/monitoring/maintenance in the cloud) while also offering the ability to self-host the same machinery.
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?
I really, really, really, really, really, really, really, really, really, really hate the design trend of confining tiny text into a tiny narrow column down the middle of my browser. It's an awful stylistic decision, and this is the petty hill I'm willing to die on. It's so bad that I really can't take a site seriously that does it.
Now, someone's going to come out of the woodwork to remind me, "Well, ackshually, research suggests that it's easier to read text that's constrained by blah blah blah blah" I don't care. It sucks. It's always sucked. It will forever suck. I have a nice 27" monitor, and I want to use the whole thing. I don't want to have to hit ctrl-] ten times just to have text that is readable and spans my monitor.
> If you have a feed reader system there is no need to subscribe [via YouTube] in the first place. You’ve obviated that system.
This approach works, and it's a great way to subscribe to public channels without a YouTube account. The main reason I'm not doing it is that I want to subscribe via YouTube.
> It would be great if it was more discoverable
Oh, hopefully there's a browser extension that detects feeds on a page and lights up and provides a menu. Shame that the YouTube mobile app isn't similarly extensible.
I wrote a program that exposes my YouTube subscriptions as a news feed. It's seriously a relief to finally have this stuff show up in [my feed reader](https://www.newsblur.com).
It's not a "Show HN" because there's no way for others to try it (yet).
Some things I'm curious about:
* Is anyone else here doing something similar?
* Would anyone like to use this service?
* Are there other YouTube-meets-news-feed features that you'd love to see?
I did maintain a list of all my subscriptions in FreshRSS for a while. I started doing this after I noticed Youtube was withholding videos from the subscription page and then showing them too me as something I might like on the home page. This really irritated me it broke my process for finding where I last was.
The problem was while I migrated in a big chunk using some jank javascript this wasn't a process that kept in sync and gradually over time it got out of date and the initial problem was fixed and I removed them all. I haven't yet seen an open source self hosted solution for this for getting the list and providing an Atom feed but its definitely something I want.
Hacker News still has a feed (that's the only reason why I saw this thread). And Reddit gives you a feed for your subscribed subreddits.
reply