imaging
GJSON
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
imaging
-
Seeking advice on monetizing an open-source Golang-based video transcoding project developed during university
There are a number of projects using manipulation libraries like https://github.com/disintegration/imaging which is already MIT licensed, and then there are various transcoders which I am unfamiliar with, but you will want to consider if you add enough value to make use of those unimportant to the decision to pay.
-
io.Pipe vs bytes.Buffer
Sorry for not putting this code in my post. The input isn't from an *os.File, but rather from HTTP request captured by gin and it's on MultipartForm.File. The reason being why I had to do all these shenanigans is because I have to preprocess the image using this module: https://github.com/disintegration/imaging
-
Tran - 🖥 Securely transfer and send anything between computers with TUI.
Imaging
- Image manipulation with Go
- Image filters / image editing
GJSON
-
Rob Pike: Gobs of data (2011)
Someone made a benchmark of serialization libraries in go [1], and I was surprised to see gobs is one of the slowest ones, specially for decoding. I suspect part of the reason is that the API doesn't not allow reusing decoders [2]. From my explorations it seems like both JSON [3], message-pack [4] and CBOR [5] are better alternatives.
By the way, in Go there are a like a million JSON encoders because a lot of things in the std library are not really coded for maximum performance but more for easy of usage, it seems. Perhaps this is the right balance for certain things (ex: the http library, see [6]).
There are also a bunch of libraries that allow you to modify a JSON file "in place", without having to fully deserialize into structs (ex: GJSON/SJSON [7] [8]). This sounds very convenient and more efficient that fully de/serializing if we just need to change the data a little.
--
1: https://github.com/alecthomas/go_serialization_benchmarks
2: https://github.com/golang/go/issues/29766#issuecomment-45492...
--
3: https://github.com/goccy/go-json
4: https://github.com/vmihailenco/msgpack
5: https://github.com/fxamacker/cbor
--
6: https://github.com/valyala/fasthttp#faq
--
7: https://github.com/tidwall/gjson
8: https://github.com/tidwall/sjson
-
Jj: JSON Stream Editor
```
I don't think there is a way to sort an array, though. However, there is an option to have keys sorted. Personally, I don't think there is much annoyance in that. One could just pipe `jj` output to `sort | uniq -c`.
[0]: https://github.com/tidwall/gjson/blob/master/SYNTAX.md
-
Library to analyze an arbitrary JSON string
I’m using GJSON, so far so good!
-
Mapping json fields in api calls to a struct to store them in a database or cache
If the fields you need are just a small subset of the whole json, maybe https://github.com/tidwall/gjson might be of use to read only those (using jsonpath) without needing to create complete corresponding structs.
-
Which CPU to buy based on profiling
Thank you for the reminder, it's never too much of it :) Didn't say it, but the code was pprof-iled many times and i can really say it's well optimized. I use own libraries with on-the-fly equations (sums, avgs, emas, stds, ...) wherever possible and also made custom json parser as json messages are in fixed format, so the parser is about 10x faster than gjson. I optimized it to the point that I avoided using maps, and rather iterate via slice where ever possible.
-
Jetro - transform and query JSON format
You are right, for learning purposes this fit my needs, but I can imagine an approach similar to this repo: https://github.com/tidwall/gjson
-
Any way to convert unknown/dynamic json to generic object structure
https://github.com/tidwall/gjson is a relatively sensible library if this is something you need to deal with and the structure is actually unknowable.
- Need help with getting the grandchild in nested JSON
- Double down on python or learn Go
- Ad hoc JSON parsing
What are some alternatives?
imaginary - Fast, simple, scalable, Docker-ready HTTP microservice for high-level image processing
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
gocv - Go package for computer vision using OpenCV 4 and beyond. Includes support for DNN, CUDA, and OpenCV Contrib.
go-json - Fast JSON encoder/decoder compatible with encoding/json for Go
bimg - Go package for fast high-level image processing powered by libvips C library
intrinsic
fastimage - Finds the type and/or size of a remote image given its uri, by fetching as little as needed.
gojson - Automatically generate Go (golang) struct definitions from example JSON
Primitive Pictures - Reproducing images with geometric primitives.
hub - A command-line tool that makes git easier to use with GitHub.
bild - Image processing algorithms in pure Go
ngrok - Unified ingress for developers