go VS Gin

Seems like this go runtime deadlock fix didn't get included.

Nothing new in fact, it's part of the culture. There is no "why", just "don't"s - an example among others https://github.com/golang/go/issues/45179

Not to worry, at least the Go team itself is still having trouble with its own completely uncheckable locking.

I usually see and recommend: https://go.dev/talks/2013/bestpractices.slide#1 https://go.dev/talks/2014/readability.slide#1 https://github.com/golang/go/wiki/CodeReviewComments https://about.sourcegraph.com/blog/go/idiomatic-go https://github.com/teivah/100-go-mistakes

Example of assembly in Go source code:

https://github.com/golang/go/blob/master/src/crypto/md5/md5b...

This mother of all things has a dedicated src directory, so it really comes down to each project to choose its own file structure.

There are many solutions available without requiring PHP 8.1 that have been battle tested, but it's interesting to see the direction the PHP language is going in to compete with the likes of Golang and Elixir, both of which support async programming and have done for years.

I dislike how the implicit reference-like behavior of slices, maps, channels, and function pointers confuses newcomers to the language. It would be less ergonomic to have to declare them as pointer types, but it would be more clear to readers. The language used to actually do this in its pre-1.0 infancy (example). Everything is passed by value, but the values are pointer themselves to the actual data structures.

Will change in Go 1.21

Use a library for HTTP serving, such as Gin, Chi, or Echo. I personally use Chi, as it's just the right level of abstraction for how I like to work. Despite what others say here, don't try to re-implement everything in a modern serving library using the standard library.

For building my web server, I chose to use the Gin framework as the foundation of my app. It was incredibly easy to understand and work with, and I was pleasantly surprised by how seamlessly it integrated with writing unit tests for the server. To handle the database, I leveraged the power of go-sqlite and migrate for efficient SQL queries and migrations. These libraries proved to be both powerful and user-friendly, making the development process a breeze.

Popular with a ton of features: https://gin-gonic.com/

CustomRecoveryWithWriter returns a middleware for a given writer that recovers from any panics and calls the provided handle func to handle it.

(https://github.com/gin-gonic/gin/blob/master/recovery.go)

Now that we have set up the Go environment, we can start building our API. The first step is to choose a framework. There are several popular frameworks for building APIs in Go, such as Gorilla mux, Echo, and Gin. For this article, we'll use Gorilla mux.

Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。

Correct example is here. But instead I suggest you just use unsafe.String and unsafe.Slice since runtime headers are deprecated anyway. You can find example here.

unsafe.Slice and unsafe.String came with Go 1.20 as I remember I will add that part, what do you think about Gin 1.19 bytesconv implementation? Is there a similar issue maybe?