I'd love for your next post to be a read through of the Redis source code to understand <i>why</i> it's performance characteristics are different than yours. I assure you that it's not out of laziness or naivite :)<p>Writing your own implementation of something is fantastic way to learn. So is reading a good one.
Flagged because without code or even binaries there's no way to learn anything from this. Is the code memory safe? Does it gracefully handle error conditions? What tradeoffs were chosen?<p>Plenty of OSS "simple redis clones" exist with performance better than Redis. I think it would be more useful to re-post those than share this.
I'm sure people will call out performance is likely due to the different nature of the beast that is now redis -- there are lots of wire compatible implementations that are faster thant redis, with some lost affordances.<p>Either way, the templating bit on the homepage is a pretty interesting concept. Storage and templating in one with write operations in the template. Im curious how this grows out and whether it will be great or a regret. Somewhat dynamic static sites like that could be fun.
Just to note for anyone like me, Dark Reader appears to mess up the formatting of the article/website. You might need to disable it for the article to actually fill the screen and not be squeezed into a small column.
While I agree with, and share, the sentiment, and I like (in C btw) and think we should use it like Rust people do with written in Rust.. there's a bit too much pontificating going on here without going into why's and no source to show and tell. I don't mind as much the latter as the former; It leads nowhere good.<p>Also, site is rendered in a way that sucks to read.