3 ms·
Not trying to be obtuse, but that's just a subjective measure of how quick or not their algo is. It doesn't address (nor in the linked HN discussion) how effici
by teh_klev 11y ago
Not trying to be obtuse, but that's just a subjective measure of how quick or not their algo is. It doesn't address (nor in the linked HN discussion) how efficient it is in terms of burning up CPU and battery.
- formula1 11y agoIf it takes a long time, it probably means that there is a lot to calculate. If theres a lot to calculate, probably means the cpu is running full speed to get through it
- teh_klev 11y agoOh sure, I understand that, but many compression articles often focus just on compression ratios (such as this one seems to do), but have no mention of the tradeoffs to obtain these results, or compare themselves against existing and well establish algorithms. That was the point of my post.
- formula1 11y agoAh, my intention radar was off. I assumed you were making an observation but didnt jump to the probable conclusion
- Veedrac 11y agoThe link has more concrete (non-subjective) timings.