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.
I’ll be honest, I really don’t know what argument you think I’m making or that you yourself are making.
The truth here is that this software will overwhelmingly be used in an illegal manner. The creators knew that when they wrote that disclaimer and we all know that reading the disclaimer. Yet the disclaimer is still placed there like it has some reason for existing beyond allowing everyone to pretend something that is happening isn’t happening. Your comments here seem to just be continuing that charade.
I’m not even condemning this software or illegally pirating movies and TV shows. I’m just remarking on the silliness of the disclaimer.
Or does it make sense to put a disclaimer on there, not just from a legal perspective, but to actively discourage those users who haven't made up their mind already? While people absolutely can use their software for pirating content—which is in open debate about the ethics—I've known very few individuals who torrent to actually profit from others material, but I know of plenty anti-piracy advocates who use stolen content for profit.
I've also known bucketloads of people that have paid $50+ for a movie in the theater or $10+ for a rental at home, only realize how badly they were duped by the industry to give money for something that was practically garbage, which they ended up not watching anyway yet the purchase was nonrefundable, which unfortunately happens several times because of all the fake interest in something actually being advertising, which appeals to their desire to fit in. It is often very exploitative.
I've also known a descent amount of people that discovered content they found joy in by torrenting, maybe at the time being depressed... struggling to get out of bed or find inspiration, and as a result improved their condition to become pretty big supporters of those who made that content later on, which they would then gladly pay for thereafter.
Seriously, any actual good artist I've known usually would be the first to encourage someone to pirate their content because they understand that the people that like it will support them, and the people that don't... they have no desire to exploit them.
Like you can claim people shouldn't shoot up heroine, while still giving them clean needles if they're still going to do it.
A majority of people own real estate, so they're happy with the status quo. Why would you put up with even the slightest personal inconvenience from added housing, if all it got you was a reduced value of your property?
Then you layer these protections against multiple levels of government so they'd all have to be repealed together by separate legislatures before the government is allowed to do it, discouraging the attempt.
Unfortunately the spec authors think this export feature violates the spec and have threatened KeepassXC with being banned by authenticating websites[1]. This explicit support from the spec authors for client banning makes passkeys non-viable to me. The websites I log in to should not be able to restrict what clients I choose to use to manage my own data.
[1] Spec author writes, "To be very honest here, you risk having KeePassXC blocked by relying parties. ... (RPs [may] block you, something that I have previously rallied against but rethinking as of late because of these situations)." https://github.com/keepassxreboot/keepassxc/issues/10407
Basically, do what we say or expect us to have our corporate sponsors write bad press about your security.
[1] https://www.smokingonabike.com/2025/01/04/passkey-marketing-...
Put all of that together, and you get a website that queries S3 with no backend at all. Amazing.