101–110 of 361 posts
100% -- this is YAGNI (or you-aint-gonna-need-it) and should be among the first things you think about when starting a new project.
I haven't used Google sheets for maybe 2 years, didn't have the need, but week ago I needed to send customer a table that will be updated every couple of days. I was surprised how slow it is. Table has 40 lines and 8 columns, static text only, and it takes 12s until I can edit it. For what it is (adding sentence every 3 day) it's ok but if I had to actually use it for myself on a daily basis it would drive me mad.
Slightly Off Topic, are there any other online SpreadSheets other than Excel 365 and Google Sheets? Some of them are AirTable like which is CRM focus, but I just want a really simple spreadsheet that is easily accessible and not from Big Tech.
Edit: Depending on your reasons for avoiding big tech, you may want to research the owner of Only Office, which was a Russian company but apparently isn’t anymore? You might want to also try CryptPad, which is based off of OnlyOffice and recommended elsewhere in the comments (which reminded me).
Always overlooked point in these pro/anti-spreadsheet discussions: A spreadsheet gives you a DB, a quickly and easily customized UI, and iterative / easy-to-debug data processing all in a package that everyone in the working world already understands. AND with a freedom that allows the creator to do it however they want. AND it's fairly portable. You can build incredible things in spreadsheets. I remain convinced tha…
They can emulate behaviour of databases; but the missing parts missing will haunt you. Spreadsheets are a jack of all trade, mastering nothing, haunting you with everything;.an amplifier for the Dunning–Kruger, where people are misguided about data-quality.
Spreadsheets are indeed a great tool, but the implementations we have today are bad, with too many booby traps, not enough safeguards, not even much comfort for those with higher demands.
Always overlooked point in these pro/anti-spreadsheet discussions: A spreadsheet gives you a DB, a quickly and easily customized UI, and iterative / easy-to-debug data processing all in a package that everyone in the working world already understands. AND with a freedom that allows the creator to do it however they want. AND it's fairly portable. You can build incredible things in spreadsheets. I remain convinced tha…
Always overlooked point in these pro/anti-spreadsheet discussions: A spreadsheet gives you a DB, a quickly and easily customized UI, and iterative / easy-to-debug data processing all in a package that everyone in the working world already understands. AND with a freedom that allows the creator to do it however they want. AND it's fairly portable. You can build incredible things in spreadsheets. I remain convinced tha…
> especially so for people who can't code. And for those who can, Appscript gives your spreadsheet super powers. For those who don't know, you are not stuck with writing JS in the Appscript integrated web IDE that comes with Google sheets (though honestly it's not too bad itself). Using clasp, you can develop your code locally in an IDE of your choice, in typescript and have a build step compile those to js, and have…
1) Everything runs on the server, including triggers and even custom functions! This means every script call requires a roundtrip, every cell using a custom function requires a roundtrip on each change, and it feels much slower than the rest of the UI.
2) You can't put a change trigger on a cell or subset of cells, only on the whole sheet. So you have to manually check which cell the trigger happened on.
3) Reading and writing cell values is so slow (can be a second or more per read or write) that the semi-official guidance is to do all reads in a bunch, then all writes in a bunch. And it's still slow then.
4) A lot of functionality, like adding custom menus, silently doesn't work on mobile. If your client wants to use Sheets on mobile, get ready to use silly workarounds, like using checkboxes as buttons to trigger scripts and hoping the user doesn't delete them.
Overall I got the feeling that Google never tried to "self host" any functionality of core Sheets using Apps Script. If they tried, it'd be much faster and more complete.
Always overlooked point in these pro/anti-spreadsheet discussions: A spreadsheet gives you a DB, a quickly and easily customized UI, and iterative / easy-to-debug data processing all in a package that everyone in the working world already understands. AND with a freedom that allows the creator to do it however they want. AND it's fairly portable. You can build incredible things in spreadsheets. I remain convinced tha…
Yeah a DB where any user can accidentally hit the spacebar and erase a formula, and never see any warning that their outputs are now horribly inaccurate.
Always overlooked point in these pro/anti-spreadsheet discussions: A spreadsheet gives you a DB, a quickly and easily customized UI, and iterative / easy-to-debug data processing all in a package that everyone in the working world already understands. AND with a freedom that allows the creator to do it however they want. AND it's fairly portable. You can build incredible things in spreadsheets. I remain convinced tha…
> spreadsheet gives you a DB Yeah a DB where any user can accidentally hit the spacebar and erase a formula, and never see any warning that their outputs are now horribly inaccurate.
What Problem?
Always overlooked point in these pro/anti-spreadsheet discussions: A spreadsheet gives you a DB, a quickly and easily customized UI, and iterative / easy-to-debug data processing all in a package that everyone in the working world already understands. AND with a freedom that allows the creator to do it however they want. AND it's fairly portable. You can build incredible things in spreadsheets. I remain convinced tha…
> especially so for people who can't code. Presumably those people learned to use a spreadsheet. What makes learning spreadsheet formulae possible, but SQL, Python, or R impossible?
One day you are writing ‘sum(a2:a201)’ the next you do some conditional formatting and so the complexity builds up very slowly with your needs.
With sql, day one:
‘SELECT SUM(Column) AS Total FROM Table;‘
Way more complicated. Way more powerful too, but most people don’t need the power until much later.
And you have to work in the console which is an unfamiliar ui for many.
It’s not impossible, but very high overhead in comparison.