re: Long details about rust sucking again
- replies
- 1
- announces
- 0
- likes
- 1
re: Long details about rust sucking again
@nytpu I see now, thanks! It’s really unfortunate, I can feel your pain :/ I’m a bit tired now so I just looked fast, but it seems that brave developers decided to not just gzip the serialized data, according to this method documentation[¹]: The data format generated from this method is not just a gzip compressed version of serialize_raw
; it is a distinct format.
[¹] https://github.com/brave/adblock-rust/blob/master/src/engine.rs#L90
re: Long details about rust sucking again
re: Long details about rust sucking again
@nytpu oh yes you are right again, (but unfortunately I have seen this also in other codebases using other languages). I really like the mentality of the following post https://lukeplant.me.uk/blog/posts/docs-or-it-doesnt-exist/ but at the same time I understand that we are all human being, and the brave developers maybe where in a hurry, and the also say in the same docstring
re: Long details about rust sucking again
@nytpu This method will be removed in a future release. Going forwards, if you’d like to use a compressed binary format, use serialize_raw
and bring your own compression/decompression. So maybe Qutebrowser should not use this at all, but again I can’t talk about what other people choose to do in their free time :) You could, for example, open an issue on Qutebrowser to ask them to not use that method, so interoperability will increase.