I’m vibecoding an excel in rust, for roughly the same reason in this post: what can’t be done, what are the limits.
https://github.com/scosman/freecell
So far it’s GPU accelerated (GPUI), cross platform, supports 95% of excel functions, supports charts, is about 40x faster than Numbers, and can render 240fps.
I thought I’d leave this process with a new appreciation for manual dev/details. I haven’t found that yet. I’m getting more into architecture details, writing more benchmarks, testing more. I know there are limits, but I’m still trying to find them.
It would be absolute garbage if I wasn’t already and engineer. It probably is absolute garbage in ways I don’t know because I haven’t read the code. But the app is… quite good.
No screenshots to see what it looks like that I was able to find?
Haven’t really promoted it at all. Here’s an older video from discord pre-charts: https://media.discordapp.net/attachments/1206947691058171907...
I like to make fun of Excel as much as the next guy and I realize my use of tabular data is very limited compared to the full abilities within the app, but what in the world in Excel needs to be rendered at 240fps?
It absolutely doesn’t need to be. This is an exercise in “why not”.
I get that, but I guess what I'm really asking is what is getting updated at 240fps? I could generate a black image and claim extremely HFR as no pixels are being updated. Maybe my not being a UI type to even know the intricacies of app UI refreshing, but 240fps to generate static text seems low to me as a bragging right
oh, scrolling around is buttery smooth.