we do this not because it's easy, but because we thought it would be easy, and once we realized it wasn't easy at all we were in too deep to get out without having to admit we were wrong about how easy it was going to be
Me yesterday spending way too many hours to make an NW.js (nodejs webkit, not-quite-electron, but more raw) rpgmaker game load in firefox because uhhhhh... why not
It did load, sorta kinda.
I might have created some deep horrors beyond one's imagination, as well. You know how Promises can't be handled from non-async context? And how a bunch of Node.js APIs are very much synchronous at random spots?
Yeah so I found out that XHR can be forced to be synchronous :D
And then I remembered about Service Workers...
