201–210 of 225 posts
My current issue with Google Sheets is that it gets really slow when I connect tries to load data from dozens of sheets into a single one using multiple importrange. Does your solution work better for this use case?
Not trying to relate with AI, GPT, or LLM in a spreadsheet product is the best thing to me, kudos!
We will add a little tasteful AI stuff later, but it's not the highest priority. Top priority is big data and fast data. AI is relatively easy to layer on later.
Earlier quoted context omitted.
Thanks! A digressing question. How does one go about learning to build an amazing platform line Row Zero?
We were fortunate to work in AWS which has some of the gnarliest datastructures and algorithms problems in the world, so we got really good there. Spreadsheets are really just more datastructures and algorithms on the backend. Our frontend guy is brilliant and built a lot of awesome stuff at Airtable, but I can't speak to the craziness that is high-complexity high-performance frontend. But it's absolutely necessary t…
Can you share some of the books that can help with this? Which algorithms were used, how etc.
Thank in advance, I am using Row Zero since yesterday and loving it thoroughly.
Earlier quoted context omitted.
I've found that while people don't want to change out of Excel they are forced to by the size of new files. The more data is generated by computers, the less likely it is to fit in Excel I imagine many professions won't be able to use Excel in 10 years based on this trend.
Unless Microsoft invests in changing that situation.
Unless Microsoft invests in row zero as a "distribution partner" as it did with Mistral, you mean: Row Zero, available now on Azure.
There, I fixed it for you.
Earlier quoted context omitted.
> Right click A0 and click "insert row above" Instead, right click A1 and click "insert row above". Google Sheets (and, I'm 99.99% sure, Excel) adjust the range inside the SUM to be three rows high. I've put quite some time into this sort of thing too :)
Didn't know who I was talking to, looked you up now, amazing ;) Thanks a lot for the bug report. We actually used to implement the range-extension logic in Excel/Sheets but removed it during a cut-paste refactor due to the complexity (I'm sure you know...) and resolved to add it back when someone asked for it. I actually found edge cases where Sheets and Excel don't do range extension logic the same way. So we don't…
if I highlight a range of cells to copy something to, only the last cell will be populated?
Earlier quoted context omitted.
Unless Microsoft invests in changing that situation.
>Unless Microsoft invests in changing that situation. Unless Microsoft invests in row zero as a "distribution partner" as it did with Mistral, you mean: Row Zero, available now on Azure. There, I fixed it for you.
Honestly, I'm really excited about this next generation of spreadsheet software. - Causal.app - Rows.com - Equals.com - and at least 50 others I've found I'm waiting for someone to create a really high performant spreadsheet engine that runs in WASM to power even more spreadsheet-y applications. The direct manipulation of spreadsheets is super underrated.
I just wonder how come there is market for these when Microsoft has Excel online. Any company that has O365 has Excel online as well.
Earlier quoted context omitted.
Didn't know who I was talking to, looked you up now, amazing ;) Thanks a lot for the bug report. We actually used to implement the range-extension logic in Excel/Sheets but removed it during a cut-paste refactor due to the complexity (I'm sure you know...) and resolved to add it back when someone asked for it. I actually found edge cases where Sheets and Excel don't do range extension logic the same way. So we don't…
I can't copy and paste formulas to more than one cell at a time? if I highlight a range of cells to copy something to, only the last cell will be populated?
In the mean time you can still paste the formula to the top cell then drag it down or ctrl+D as a workaround, but we want to support the full experience, so check back in a few days and it should be there :)
Earlier quoted context omitted.
We were fortunate to work in AWS which has some of the gnarliest datastructures and algorithms problems in the world, so we got really good there. Spreadsheets are really just more datastructures and algorithms on the backend. Our frontend guy is brilliant and built a lot of awesome stuff at Airtable, but I can't speak to the craziness that is high-complexity high-performance frontend. But it's absolutely necessary t…
Excuse me for probing further. Can you share some of the books that can help with this? Which algorithms were used, how etc. Thank in advance, I am using Row Zero since yesterday and loving it thoroughly.
For a project that will teach you literally everything there is to know about backend development:
1. Write a simple PUT/GET/DELETE REST API network layer, this should be a few hundred lines of code max depending on how much you choose to lean on libraries vs write it yourself
2. Then, write a simple in-memory blob store behind the PUT/GET/DELETE REST API. Just use a very simple hashmap of keys to data. You now have an in-memory S3 mock!
3. Now, rather than in-memory hashmap, start saving the files to disk. Write code that allows you to start and stop the process and recover all the data from disk. Now you have a persistent S3 mock.
4. Now, start finding the limits of this application. Write a program that calls your API with different usage patterns to load test it. Find the limits.
5. Now start optimizing. You can go as far as you want here. This optimization process was my whole career at AWS S3, and most of it at Row Zero.
6. If you want to really learn some advanced data structures and algorithms, stop using the filesystem directly, and write your own storage mechanism. Allocate 1 giant 16GB (or however large) file and store all of your blob data inside that 16GB "partition". You have to do all the serialization and retrieval etc yourself.
Your filesystem is already doing this for you when you store as files (look up how the ext4 filesystem works, inodes, pages, etc). But your filesystem is probably optimized for consumer use, not this blob-storage system use.
So you can implement your own much faster version if you want. If you want to really learn datastructures and algorithms, try to code a simple Log Structured Merge Tree. This will teach hashes, trees, bloom filters, serialization, deserialization, etc, all with high performance in mind.