Menu

What are companies actually using for http in production right now? Feeling like I'm reinventing the wheel with net/http

Reading 0:00
15s threshold

I’m learning Go with the goal of becoming employable, but most reddit discussions comparing frameworks seem to be 3 to 4 years old.

Now that modern Go has added method matching and path routing directly into net/http, a lot of advice says to just stick to the standard library. However, whenever I try building a practical API with pure net/http, I feel like I'm constantly reinventing the wheel. Writing custom response wrappers just to capture status codes for logging.

For those of you working with Go professionally:

  1. Is that reinventing the wheel boilerplate normal in production, or do most teams just reach for a router/framework?
  2. What are companies actually building with right now? Pure net/http, Chi, Echo, Gin, or something else?
submitted by /u/SowertoXxx
[link] [comments]