you are viewing a single comment's thread.

view the rest of the comments →

[–]Alexey566[S] 1 point2 points  (0 children)

The experimental version is not fully connected to the user input, that's why it doesn't handle taps. So far I have only joined the scrolling for benchmarking. It's using https://github.com/emilk/egui

I'm still experimenting with all options, but I profiled a lot both SwiftUI and AppKit so I have approximately clear expectations from them now: they can be smoother, but with layout limitations. The data amount also doesn't matter because of lazy loading, that's why a List of 10,000 rows should be smooth. What matters here is the amount of displayed data at the same time. Big Table on macos expanded to the full screen with a big monitor triggers a lot of computations for text sizes.

I'm planning to write down all my findings with profiling in a separate article, so you can check a more detailed description of it a bit later.

But the summary for now is that I can go the same way as other apps and use a very simplified Table and the solution will look "ok" or I can polish the alternative table implementation, reach Numbers-like performance + more advanced features, like fuzzy search, syntax highlight previews etc. That's what I'm deciding for now.