Jeremiah Senkpiel

See https://github.com/http-rs/tide-websockets/issues/23#issuecomment-996110797 for the root of this issue. Sadly, I don't work on this anymore. Maybe I should have asked about moving it to my personal before I left Eaze....

This is mentioned in https://github.com/eaze/tide-sqlx/pull/4/commits/570dbc13de940054ab1a19dae57cb3a5754fc98d, but should be in the docs. This is unfortunately impossible to support in current Tide. All middleware must be able to be `Send + Sync...

Personally, I'm kinda ok with whatever structure will enable me to be more effective here. I would like to reiterate a couple things about my involvement in Node.js: - I...

Will you fund the development of this? 😉 Seriously though this would be a gigantic undertaking.

There are some areas that threading, or rather, full or partial workers would be useful in. Partial, or rather, computation (non I/O access) workers are probably reasonable to implement and...

I mean, Ayo really isn't constrained with user breakage they way Node is, so... migrating to module mode as a default is probably _possible_. It probably won't be nice either...

Could you please describe in more detail how this would work / what you are looking for?

This is more-or-less requesting a port of https://github.com/nodejs/node/pull/5020, which didn't land in Node at the time. > This sounds like a pretty neat feature. Would be interesting to see how...

The reason we didn't for node boils down to two things: - Git is easy recoverable because the repository is fully distributed to whoever clones it. Any one of us...

From https://github.com/ayojs/ayo/pull/22, the current plan is to rebase commits from upstream Node *ontop* of our commits.