a way to use TextKit 2 without compromising user experience?
https://blog.krzyzanowskim.com/2025/08/14/textkit-2-the-promised-land/
Just recently, @dimsumthinking brought something up in a talk on SwiftData. Basically: this is cool, but is Apple committed to it?
Too quick to release new stuff, too quick to abandon existing stuff.
I do think that the viewport based approach is good and can have great results, but that it's the internals of this particular implementation that are the problem.
CodeMirror has a nice implementation (haven't looked for a few years, but I'm sure it's still good) that I don't think suffers these issue.