bindata VS net-http-server

I recently ditched bindata for a self written solution because I couldn't figure out why exactly it leaks memory. According to count objects it creates a shit ton of classes if you read a lot of data and idk why

"Writing an entire custom program" is the best way. Ruby has a nice package called bindata (https://github.com/dmendel/bindata) that works well for this purpose.

For example, I enjoy sim racing, and some of my games provide a network API for things like telemetry data. So I wrote a simple telemetry logger that I use to gather data, which I then mess around with using R Studio. Ruby worked exceptionally well for this because of a cool little library called BinData.

These projects always remind me of binary formats. I've used bindata to work with binary formats coming from UDP streams over a network, and it's very handy to have a layer that encapsulates your expectations about the data you're receiving, combined with an exception handling apparatus.

Yes, I actually have. Implementing a basic HTTP parser isn't that difficult, once you implement the correct parsing rules from RFC 9110. If you want to fully support the HTTP protocol, you also have to implement things such as Chunked Transfer Encoding or Gzip Deflate.