I blame a substantial portion of the internet's decline on the failed IPv6 transition and this video sent me into a minor doom spiral.

https://www.youtube.com/watch?v=Sm1HjdmoeeA

I never built anything more complicated than a static site until college and I haven't carried any of those applications forward.  My early interest in onion routing was because I thought I could actually run a publicly accessible service through it.

Whenever someone asks me how to build a website or if I'll build one for them, I say "you don't need me, there's free tiers for xyz and you'll probably fit within them."

Of course I would never use these products.  Because I worry about the tracking, I worry about the politics of the owners, I worry about lock in, I worry about the format of data, and I worry until I'm stuck: a valid enough reason to close of every door or path.  And I might as well not build anything.  A younger, smarter, capable, person could do a better job anyway.

Why is this posted on a Blogger blog then?  I don't know.  I keep this as an outlet for self harm.  When I can't stand it anymore I'll make a draft.  I hate the tracking it does for readers.  I hate the fucked up XML templating system.  I hate the divs and css classes that it forcibly inserts into the page which are dogshit, unsemantic, wastes of bytes.

 I use blogger and I think about how it's a monument to Google's malice.  I use blogger and I think about how the LLMs can and do write better software then this.  I use blogger and I wish a swift LLM assisted unemployable layoff for all programmers, a pointlessly poetic end for the people who had so much power - that ability to wield "pure thought stuff" - and chose to use it to degrade and devalue every other profession.

If the internet is just going to continue devolving into "eyball" networks and "content" networks then I'm done.  Pathetic, but I'm done.

Think about these things first before adding a CSS class to your HTML element.

Should I be using this HTML tag or is there a more appropriate element?

Read through the list of HTML elements and see if a closer match exists. You should have at least one <main> tag on your page, and probably at least one <header> tag too. Almost every website should have at least one <nav> and you may want to add some <article> or <section> tags.

I bought a Raspberry Pi 3 B+ a few years ago about the time I started learning Rust which was also about when I took OS dev. I wanted to learn OS development and I’d heard about CS140e so I thought it would be relatively easy. And it has been relatively easy when compared to interchanging the OS on my laptop which is the alternative I was considering. The Raspberry Pi has a lot of tutorials and examples, it’s hard to brick, it can netboot, it has user and kernel mode, and it has GPIO that would be fun to play with.

There are plenty of ways to build reactive interfaces, but my favorite is to use finite state machines. I've written before on how JavaScript Promises are finite state machines, but I only briefly touched on how finite state machines communicate between each other. With communication comes the potential for race conditions and race conditions bring sadness.

There was an old trick used by Angular and a few other libraries of using a function's source code (which you can get using .toString()) to get its argument names. Promisify-node used this technique to find arguments called callback or cb. Angular uses it for dependency injection, though there are other better ways of doing that.

I’ll be using JavaScript here. With it we can write this in <100 lines of code.

Harness

We’ll start by laying out our code. I’ll be using closures, but you could — and my first version did — use a class instead. We’ll need a parse_html function, inside we’ll put a helper function called pull and a parse_content function which we’ll fill in later.

If you’d like to follow along, the finished code is here: regex-html

I'm excited about template elements. There's no specified way of instantiating them, so let's talk about where they come from, why we use them, and how to instantiate them.