3 ms·
I followed your link which leads me to rant a bit: LZFSE has been out since one year. Not one mention on wikipedia. The repo lacks a good description what lzfs
by legulere 10y ago
I followed your link which leads me to rant a bit:
LZFSE has been out since one year. Not one mention on wikipedia. The repo lacks a good description what lzfse is. It also contains a LZVN encoder/decoder. The only information I found about it is some blog where someone seems to reverse engineer it for some hackintosh purposes.
I know documenting and presenting the case why people should use your software/file format can be annoying to do, but it's really important.
- js2 10y agoWWDC video talking about it: https://developer.apple.com/videos/play/wwdc2015/712/ https://developer.apple.com/videos/play/wwdc2015/712/ Apple's docs: https://developer.apple.com/library/mac/documentation/Performance/Reference/Compression/ https://developer.apple.com/library/mac/documentation/Perfor... Generic info on finite state entropy compression: http://fastcompression.blogspot.com/2013/12/finite-state-entropy-new-breed-of.html http://fastcompression.blogspot.com/2013/12/finite-state-ent... The last link was submitted to HN: https://news.ycombinator.com/item?id=7040951 https://news.ycombinator.com/item?id=7040951 The repo's README seems pretty clear. Google provides the rest. Not really sure how much more there is to say about a reference compression algorithm.
- AceJohnny2 10y agoThose first two links should ideally have been included in the project's README. From a maintainer's perspective, "Google it" should never be acceptable.