goodbye blazor

i've done it for the bit long enough, now makko is my friend :)

• #dotnet
• #meta

for quite a while i used blazor ssr to host my personal website. i honestly don't think it was practical at all, at idle it uses around 207M of memory, which is a lot for a glorified static site. however i had been spending a lot of time contributing to iceshrimp.net and saw its maintainer, zotan, was using razor pages for her site and i thought it would be fun to do it for the bit.

the site was honestly pretty scrappy, it had all of the functionality of this site but with a significantly higher level of complexity in the backend. posts were generated from markdown using a service which would search the BlogPosts directory at startup for markdown files and parse them using markdig (which now has a permissive ai contribution policy). this is almost certainly where all of that memory usage comes from, as it would store all of the pages in a dictionary and retrieve them when a page with a matching slug was requested. i wasn't particularly bothered with the resource usage of my site and would take shortcuts until i ran out of foots to gun.

in comparison, makko is a small static site generator written in zig that has all of the features i was writing with shitty c# code. it converts markdown to html, generates atom and rss feeds, supports mustache templating, and lets you define custom data structures in its project file. it also has hooks for page creation, modification, and deletion which could be useful for automating workflows.

now that i've ported my website for the 50th time i'm probably gonna go back to not touching it, just like any other self respecting web developer. at least i don't have to worry about resource usage anymore though. but for real check out makko, give them a gold star, and subscribe to my atom/rss feeds :3