/explore
|
You are here 
|
aarol.dev | ||
| | | | |
hjr265.me
|
|
| | | | | I know many will start with something like Gin whenever they are working on a JSON/HTTP-based backend in Go. I, not entirely sure if the minority, try to stick to Go's built-in net/http package and, at most, use Gorilla Mux in most of my Go projects. And so serving something simple like JSON is no different from the package's point of view as any other content type: whatever it is, write it out to the w, the http. | |
| | | | |
xnacly.me
|
|
| | | | | Guide about working with JSON in go with HTTP server example | |
| | | | |
mmhaskell.com
|
|
| | | | | [AI summary] A tutorial series begins by defining custom Haskell data types to parse HTTP 1.1 requests and responses from scratch, focusing on the underlying protocol mechanics. | |
| | | | |
soatok.blog
|
|
| | | Programmers don't understand hash functions, and I can demonstrate this to most of the people that will read this with a single observation: When you saw the words "hash function" in the title, you might have assumed this was going to be a blog post about password storage. (Passwords are the most common knee-jerk reaction... | ||
