Monday, March 13, 2023
HomeGolangGorilla Toolkit remains in Archive Setting - Technical Conversation

Gorilla Toolkit remains in Archive Setting – Technical Conversation

I’m uncertain it was uploaded below 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 message:

I want hearing your responses to this when it come to just how it influences jobs making use of the gorilla toolkit. I’m possibly not mosting likely to make use of gorilla/websocket moving forward (seriously, however, what’s the different now?) because that will possibly require to alter with time. Nevertheless, I have numerous jobs making use of gorilla/mux as well as I’m uncertain I will certainly be moving them to something various for the near future. I indicate – just how frequently does an http router truly require to alter?

For brand-new jobs, it’s possibly secure to still make use of gorilla/mux if you recognize with it. It’s utilized by a great deal of jobs as well as I need to envision 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). Yet I wonder to recognize what other individuals on the online forum are doing.


Most Popular

Recent Comments