Login
You're viewing the mastodon.dunklecat.dev public feed.
  • Sep 4, 2026, 11:11 PM

    one of my challenges in my projects, as I set out to define the constraints to which I want to define my goal for a new personal computer for me by me, is that I have a lot of experience with a lot of different tech - different languages, different operating systems, different application stacks, what have you - so when I’m asking myself what I need to do what I want it’s easy to bring concepts and capabilities over together rather than just specifying the capability and letting the concepts be reconsidered during implementation, yeah?

    like, as an example, I am going to want programs to be able to store data in databases. I know a lot about a lot of different databases! it would seem to make sense for me to just bring one or two of the databases that I already have experience with over to my new operating system, but that’s a misstep in my opinion, for a couple reasons.

    first, modulo some very specific database engines, most database systems in the modern age do not live in a vacuum, so you are implicitly signing up to support their entire dependency stack into your new thing. so, postgresql is great, but probably not what I need on my personal computer.

    libsqlite might be a better fit, smaller, simpler model, yet sufficiently databasey, right?

    yeah, what if that’s still more database than my personal computer needs right off the bat?

    we can go smaller.

    💬 1🔄 0⭐ 0

Replies

  • Sep 4, 2026, 11:12 PM

    but there’s absolutely no need whatsoever until I have some part I want to implement that’s gonna need some sort of database!

    shave that yak in its day, friend! why the crap am I worrying about whether or not to have a relational database management system on my personal computer?

    smaller.

    💬 1🔄 0⭐ 0
  • Sep 4, 2026, 11:17 PM

    when the day comes, way down the line, when I end up saying “well, yep, I really wish I just had a database I could use for this”, that’s the day I can start to sit and re-evaluate how I feel about the current state of relational database technologies and SQL and noSQL and others and then decide what I want my database to look like and feel like and provide for the stuff I want to do with the ecosystem I’ve built to that point in mind and proceed from there.

    it’s my personal computer. it only has to comply with exactly as many standards as I say, but it has a whole world of standards to choose to implement should I decide I want that functionality. it doesn’t have to be as overwhelming as it may seem at the first thought of “wait build a personal computer and operating system?”

    💬 1🔄 0⭐ 0
  • Sep 4, 2026, 11:25 PM

    and honestly, one of the specifications that I’ve given myself for the completed projects is a full-on cheat code as well as a quick on-ramp for some hands-on-device testing throughout the projects lifetimes.

    one of my requirements is that I want to be able to use the keyboard, trackball, and display of my personal computer to connect over VNC to remote computers. it absolutely requires a standards-compliant vnc protocol client program. so I’m gonna be on the hook to implement that. I haven’t written a vnc client yet, but when I get to that point I will; it’s a knowable spec to hit, and if I’m not planning on trying to impress anyone with it I can even skip the parts of the spec that I know I’m not gonna need for my use case.

    smaller.

    but then, I have the ability to lean on “old ways” by remoting into my current laptop and using its linux environment to do whatever it is I’m trying to do that my new personal computer system isn’t equipped to do yet, and every time I have to fire up the vnc client it’s an opportunity to identify an eventual TODO for me to get to so I can move my personal computering off of the current platforms and onto mine over time, at my pace, without any more artificial deadlines than necessary. gently, thoughtfully, exploring the possibilities for my personal computering.

    💬 1🔄 0⭐ 0