Randal L. Schwartz

A few days ago, an article by Flutter developer Hammad Tariq caught my eye: "Rendering 10,000 Machine State Changes on a Timeline Without Freezing Flutter".

It was a solid piece of profiling detective work. Hammad was building a high-density timeline view in Flutter representing 10,000 machine state transitions. But every time the dataset loaded, the mobile UI stuttered and dropped dozens of frames.

Under a section aptly titled "The Original Sin", the author identified the culprit:

sorted.sort((a, b) => DateTime.parse(a.start).compareTo(DateTime.parse(b.start)));

Because sorting makes O(N log N) comparisons, sorting 10,000 items was triggering over 215,000 redundant calls to DateTime.parse() right inside the comparison callback, blowing past the 16ms frame budget and freezing the screen.

To fix the frame freeze, Hammad introduced a clever optimization: map each item to a temporary helper object holding the pre-computed timestamp, sort the list using that cached value, and unwrap it:

// Step 1: Map to a wrapper holding the pre-computed sort key
final parsed = widget.activity.map(_ParsedActivity.new).toList();

// Step 2: Sort using the cheap, cached key
parsed.sort((a, b) => a.startUtc.compareTo(b.startUtc));

// Step 3: Unwrap and process down the pipeline

The UI freeze disappeared. The timeline ran smoothly.

When I read that section, I couldn't help but grin. Watching an engineer independently discover an algorithmic optimization from first principles is pure joy--especially when it's the exact Map → Sort → Map idiom I posted to Usenet (comp.lang.perl) back in 1994, which Tom Christiansen dubbed the Schwartzian Transform!

I dropped a friendly comment on the article letting them know their optimization has a 32-year history. And then I wrote up a full deep dive exploring how modern Dart 3 language features--specifically Records and Extension Methods--bring the idiom full circle, turning it into a type-safe, zero-boilerplate one-liner that runs 13x faster than naive sort.

I also dive into why Dart's official package:collection sortedBy() method doesn't cache keys either (and still burns 127,000 redundant evaluations), and link to the classic History of the Schwartzian Transform on Perl.com.

Whether you know me from the Camel and Llama books or my recent work as a Flutter GDE, it's deeply satisfying to see a 1994 Usenet idiom still saving CPU cycles on a 120Hz smartphone display in 2026.

Read the full article with benchmarks and code on DEV.to:
https://dev.to/gde/rediscovering-the-schwartzian-transform-why-i-had-to-comment-on-a-flutter-performance-article-30l0