So I took @warrenm's MetalSlug (https://github.com/metal-by-example/MetalSlug) - itself an implementation of the https://sluglibrary.com paper…

Ported it to https://metalsprockets.com

Optimised it so it renders all text in a single draw call (from an original 40,000 draw calls…)

And then entered the matrix?

Every glyph is vector. Whoa.

(Code needs a cleanup - it got messy but will put it online soon)

A completely vector based terminal view eh @Migueldeicaza? Or did the work you do recently use SLUG?
@schwa wow, my thing uses rasterized bitmaps and the atlas. This is so cool
@Migueldeicaza Not at all optimised - but concept works. 40fps on a M5 Max isn't great.
@schwa omg this is sublime. I love this

@Migueldeicaza Ok - 60fps, should easily manage 120fps when I am not plugged into that speed bump of a Apple Studio Display.

(Big difference running release vs debug - those Swift arrays are slooow. And a couple of obvious optimisations).

Not sure if SwiftTerm needs this but can look into contributing.

@schwa @Migueldeicaza have you all tried any of the noncopyable containers we've been working on in https://github.com/apple/swift-collections?tab=readme-ov-file#basiccontainers-module for your hot paths
GitHub - apple/swift-collections: Commonly used data structures for Swift

Commonly used data structures for Swift. Contribute to apple/swift-collections development by creating an account on GitHub.

GitHub
@joe @schwa oh I had not! I need to pay more attention, which ones there?
@joe @schwa oh RigidArray! Will check it out! That’s exactly what I need