Yep, yep, I understand the reasons. That's why in where I work we decided to use asyncify because COOP is very strict for us It has a penalty on cold start, but once many blocks cached it works perfectly, without event loop interruptions
You're not the only one :/. We suspect that the COOP/COEP requirement for OPFS will be outright untenable for many folks, in particular those using hosting which does not offer them the option of modifying outbound headers (in fact, we had to extend sqlite.org's http server, althttpd, to add that capability for this purpose!). We've brought this pain point to the OPFS folks' attention but there is currently simply no way around it.
