Re:IndexedDB is completely broken in latest Safari
by magicalhippo on Tuesday June 15, 2021 @09:41AM
(#27515385)
Why? At work we've had several cases where one API (or similar) turned out to be completely broken, yet we successfully implemented a workaround using another API.
That doesn't change the fact that the API we initially tried to use was completely broken.
Like, maybe the service we needed to supply with data had a REST API which turned out to be completely broken, so we ended up reverting to generating XML files and uploading that via SFTP. That the data ended up where it needed to doesn't change the fact that their REST API was broken.
Re:IndexedDB is completely broken in latest Safari
by Tepix on Wednesday June 16, 2021 @06:45AM
(#27526980)
In this case it seems like a retry will change this API from "completely broken" to "working again".
Re:IndexedDB is completely broken in latest Safari
by magicalhippo on Wednesday June 16, 2021 @08:05AM
(#27527560)
How so? I didn't mean broken as in the web server didn't respond or service wasn't running. I meant the API was broken, as in did not do the right thing.
Re:IndexedDB is completely broken in latest Safari
by Tepix on Wednesday June 16, 2021 @02:34PM
(#27531877)
To ke "completely broken" means "broken beyond repair"
Re:IndexedDB is completely broken in latest Safari
by magicalhippo on Wednesday June 16, 2021 @03:27PM
(#27532441)
That's not a definition I would agree with. Completely broken to me, in the context of API's at least, means it doesn't do at all what it is supposed, or documented, to do.
A file server which claims to store files for late retrieval but saves all incoming files to /dev/null is completely broken from the user POV, while it's likely not beyond repair.
That seems rather contradictory