4 ms·

I have mixed feelings about this one. It certainly has inspired some interesting discussion. The paper itself is obtuse and difficult to absorb. The methodol

I have mixed feelings about this one. It certainly has inspired some interesting discussion. The paper itself is obtuse and difficult to absorb. The methodology isn't _really_ new, but it isn't used frequently. While they showed it as competitive to commonly used sorting algorithms, situationally it can really shine and show significant performance benefits. I'm surprised they didn't show this in one of the graphs (or I missed it in my brief speed-thru). I don't really see a future for this in standard libraries. I can totally see this methodology being used in the wild in a variety of systems where time = money or entities are looking for a small proprietary distinguishing edge.

KirinDave 9y ago
The follow-up paper I linked is less massive and shows a use case that were I younger I would set out with as a startup. I'm not sure why stdlibs for some languages shouldn't take this approach though. It's difficult, sure, but so is any new foundational tech. What do you see as the barrier?
- Steeeve 9y ago
  complex to do right, limited usefulness, potential for a great deal of memory usage, lack of a common understanding of proper use cases. I can totally see it as part of any number of extended libraries. Just my opinion though. I would be happy to be wrong.