I’m unsure it was published right here so I figured I would certainly publish it. Since Dec 9, 2022 the whole gorilla toolkit remains in archive setting:
There’s a great deal of excellent conversation on this reddit blog post:
I have an interest in hearing your responses to this when it come to exactly how it impacts tasks utilizing the gorilla toolkit. I’m possibly not mosting likely to make use of gorilla/websocket moving forward (seriously, however, what’s the alternate today?) because that will possibly require to transform with time. Nevertheless, I have numerous tasks utilizing gorilla/mux and also I’m unsure I will certainly be moving them to something various for the direct future. I imply – exactly how frequently does an http router actually require to transform?
For brand-new tasks, it’s possibly secure to still make use of gorilla/mux if you know with it. It’s utilized by a great deal of tasks and also I need to think of someone is mosting likely to fork/maintain it. I’m leaning in the direction of julienschmidt/httprouter for the majority of my brand-new APIs (or stdlib). However I wonder to recognize what other individuals on the discussion forum are doing.
As a rookie I locate the constructed in mux suffices for my requirements. As well as I locate it both less complex and also a lot more adaptable both for website and also API. I have actually evaluated both gorilla and also fasthttp, however I locate them in reverse reasoning to a fresh Gopher. I never ever obtained them to function …
