The only downside is that some languages/runtimes do not automatically delete
them on close, which is annoying the next time the server starts up.
The only downside is that some languages/runtimes do not automatically delete
them on close, which is annoying the next time the server starts up.
And I imagine the cost is minimal since it does not (should not) allocate a new array and be simply a view, right?
And I imagine the cost is minimal since it does not (should not) allocate a new array and be simply a view, right?
2/ the error only includes the name of field and not its location/path, making it really confusing in complex structures.
I had high hopes for encoding/json/v2, but the discussion is stucked in limbo.
And I really do not want to write another JSON parser.
2/ the error only includes the name of field and not its location/path, making it really confusing in complex structures.
I had high hopes for encoding/json/v2, but the discussion is stucked in limbo.
And I really do not want to write another JSON parser.
- For multiple ranges, instead of just sending back an aggregate, you must format a multipart/byteranges message from hell that has to be parsed. That's why no one supports multiple ranges.
Thank you so much IETF.
- For multiple ranges, instead of just sending back an aggregate, you must format a multipart/byteranges message from hell that has to be parsed. That's why no one supports multiple ranges.
Thank you so much IETF.
Not as bad as Rubocop but still bad enough I won't use it.
Just use "go vet".
Not as bad as Rubocop but still bad enough I won't use it.
Just use "go vet".
I just realized Bluesky has a 300 character limit which is even more ridiculous that Mastodon, so I'm probably not going to bother posting here. Sad.
I just realized Bluesky has a 300 character limit which is even more ridiculous that Mastodon, so I'm probably not going to bother posting here. Sad.