| Sloppiest slop I've seen in a couple weeks: - fork of a fork of a quantization technique - Only contribution is...compiling JS to WASM by default? - suspicious burst of ~nothing comments from new accounts - 6 comments 7 hours in, 4 flagged/dead, other 2 also spammy, confused and making category errors at best, at worst, more spam. - Demo shows it's worse: 800 ms instead of 2.6 ms for text embedding search - "but it saves space" - yes! 1.2 MB in RAM instead of 7.2 MB to turn search into 1s on a MacBook Pro M4 Max, instead of sub-frame duration. - It's not even wrong to do this with the output embeddings, there's way more obvious ways to save space that don’t affect retrieval time this much |
https://teamchong.github.io/turboquant-wasm/search.html