Still plugging away on Cassava, a CSV editor that sits somewhere between sublime text and Excel: https://cassava.dev/. Our most recent releases added first-class xls/xlsx file opening and an autofill handle.
The project goals are simple:
* Treat CSV files like first-class spreadsheets; don't do anything that isn't supported by serializing to/from CSV files
* Be as performant as your favorite text editor while retaining the ergonomics of a tabular data editor
This past week I've been working on the spreadsheets in https://blackbear.app hoping to get the latest changes released sometime today -- how do you think they stack up? also how are you testing performance?
(note, you can test the spreadsheets by continuing through the login page at https://my.blackbear.app as an anonymous user)
I've got a suite of CSVs that represent both edge case and performance issues, and I script timing opening/common operations using Apple Scripting. It's not perfect, but it gives us a sense if we're introducing back-breaking regressions. I try for our large files to test specifically with real-world, large data dumps from US government sources; I feel these are representative of actual large-CSV workloads. You can see me popping off about it on bluesky: https://bsky.app/profile/wyattkirby.com/post/3mnfvma4cgk2g
We're not necessarily aiming to be the fastest application in the world; find/replace is probably still faster to just do sed in the terminal. But if you're looking to do something like sort, filter, actually engage with the tabular data, then we can handle hundreds of thousands of rows --- files that excel won't even open.
I'll take a look at blackbear. One core difference I see is that we're a native app, fully offline. There is a single handshake with the licensing server on app start, but it's optional. License validation is handled fully locally, and missing network access is non-blocking for any features.
Look cool! This might turn out to be a really nice tool to use when teaching SQL to my students. If you ever consider an educational license, of course.
The integrated SQL bench runs a full duckdb so it should be super accessible. Let me know what kind of licensing terms you'd need to make this work --- you can drop me a line at wyatt[at]apsis[dot]io.
The project goals are simple:
* Treat CSV files like first-class spreadsheets; don't do anything that isn't supported by serializing to/from CSV files
* Be as performant as your favorite text editor while retaining the ergonomics of a tabular data editor
I hope you check us out.