Show HN: We built the fastest spreadsheet
171–180 of 225 posts
Re: Show HN: We built the fastest spreadsheet
#172This would be a heck of a lot cooler if it was a local-first desktop application. It's still cool mind you, but it could have been a heck of a lot _more_ cool.
Re: Show HN: We built the fastest spreadsheet
#173Congrats! As a sheets user I appreciate that rows are seamlessly added as you scroll past the initial sheet size.
Re: Show HN: We built the fastest spreadsheet
#174Earlier quoted context omitted.
Can you make it a desktop application?
We have development desktop builds. A few product questions for you: Would you be ok with a new file format or do we need to save to .xlsx? How important is Python in a desktop version? Would you need integration with conda or virtualenv? How much do you think we should charge?
2. A lot of our sheets use VB/macros so a scripting language is pretty useful. Not sure about the other stuff.
3. No idea, around the price for an office 365 seat?
Re: Show HN: We built the fastest spreadsheet
#175Quick bug report: I set A0 and A1 to 1, then set A2 =SUM(A0:A1)+A0+A1. As expected, A2 evaluated to 4. Then I right-clicked on the 1 row header and inserted 1 row above. Expected: A3 should become =SUM(A0:A2)+A0+A2 and evaluate to 4 Actual: A3 becomes =SUM(A0:A1)+A0+A2 and remains 4 until it is edited, at which point it evaluates to 3.
I just tested in Excel and Google Sheets and our behavior matches them here, unless I am misunderstanding the repro steps. For me, A3 becomes =SUM(A1:A2)+A1+A2 and remains 4 as it should be. The action I am taking: A0=1 A1=1 A2=SUM(A0:A1)+A0+A1 (evaluates to 4) Right click A0 and click "insert row above" Now I have: A0=empty A1=1 A2=1 A3=SUM(A1:A2)+A1+A2 (evaluates to 4) Thank you for trying to find edge cases! I hav…
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 :)
Re: Show HN: We built the fastest spreadsheet
#176Earlier quoted context omitted.
If you need protection from the US security apparatus, you're not the target market.
On the contrary, that scenario (as well as, "what if your SaaS provider or CSP is hostile?"), are great "clarifying" questions to understand the security architecture of a product that is very likely to see some incredibly sensitive data. It is possible for the answer to be that a service is NSL proof -- with asterisks, and the asterisks are very interesting to discuss. And no, it's not about the US security apparatu…
with the exception of red teams, AWS isn't securing AWS from US security apparatus attack though.
Re: Show HN: We built the fastest spreadsheet
#177Earlier quoted context omitted.
This feature would be the fastest way for the company to have the least number of paying users. As a user, I'd pay for one account and then share new spreadsheets with anyone who asks for one on the Internet.
If I’m the type of user who would ever consider paying, I’m most definitely not the type of person who wants to ask a stranger on the internet to setup a new spreadsheet for me every time I want to use one. I wouldn’t even want to ask a friend or coworker.
Re: Show HN: We built the fastest spreadsheet
#178Earlier quoted context omitted.
Can you make it a desktop application?
We have development desktop builds. A few product questions for you: Would you be ok with a new file format or do we need to save to .xlsx? How important is Python in a desktop version? Would you need integration with conda or virtualenv? How much do you think we should charge?
Re: Show HN: We built the fastest spreadsheet
#179Earlier quoted context omitted.
Can you make it a desktop application?
We have development desktop builds. A few product questions for you: Would you be ok with a new file format or do we need to save to .xlsx? How important is Python in a desktop version? Would you need integration with conda or virtualenv? How much do you think we should charge?
python in the app needs to be wholly self contained so whatever the backend it uses, it's separate from anything else on the system.
charge through the nose for desktop clients because of how much it costs in development and support time. people who want native clients so it's not up on a cloud somewhere for whatever reason can pay for that privilege.