Plurrrr

When you start to build web applications with Go, one of the first questions you'll probably ask is "which router should I use?".

It's not an easy question to answer, either. There are probably more than 100 different routers available, all with different APIs, features, and behaviors. So for this blog post I've evaluated 30 popular ones, and created a shortlist of the best options along with a flowchart that you can use to help guide your choice.

Since aarch64 moved to Tier-1 for FreeBSD, it’s a good idea to also test your ports on that architecture. But if you don’t own hardware for that, you will quickly run into limitations with the qemu-user-static plus native-xtools approach for cross-building. Some ports just won’t work with this.

One possible solution is to subscribe to the Oracle Cloud. They offer some resources as “always free”; you can use them to configure one aarch64 machine with specs good enough for occassional ports testing.

At the moment, you can pick one FreeBSD RELEASE image, which will give you a root partition with UFS. For ports testing with poudriere, you will need ZFS to do it efficiently, and you should run -CURRENT to also test that. This document describes the steps needed to get there.

In 2009, I wrote a blog post How to submit a patch by email, which became popular at the time and also ended up in the PostgreSQL wiki. That article was written pre-Git and pre-cfbot, so maybe it’s time for a refresher, as we head into the next PostgreSQL development cycle.

The short answer is: Use git format-patch. That takes care of almost all of the conventions and details.