gfs

I stopped reading after I saw the bullet point stating Zig doesn't have undefined behavior.

> One database query took longer than expected. That blocked an async task. Which held up the executor.

This only happens if you're using blocking code in the event loop, right? This article seems like an admission of over-engineering from the get go.

I don't believe so. It is however shared on sourcehut.

> ...and it still results in cache-miss, even when the request comes from the same location and edge.

I'm sure they have multiple data centers in each location. Especially if it's a high traffic interconnect.

I'm failing to see how this could have as much or more utility than a Tacoma. I don't see any mention of towing or payload. Not to mention, the clearance will be limiting for anyone who wants to venture off road at all.

So the caveat is you need to call `spawn_blocking` with synchronous functions. I see.

I don't know much about what an Amish lifestyle entails but I have to imagine their limited or non-existent exposure to modern carcinogens helps as well. I think of all the awful things I've been around only to learn later it could adversely affect my health.

Where would one even start learning more about front-end development in today's world? Ignoring the dizzying amount of frameworks, how could I become knowledgeable enough to connect my back-end experience to design the "full stack?"

I would love to see a blog post or more detail about how this implementation works and why it can beat rayon in some cases.