Occasionally I think the #Fedify project might need to leave #Deno. I'm even thinking that while adding Cloudflare Workers support… 🤔

@hongminhee
we all think occasionally wrong :)

Clemens is now in Duisburg and I talked to three people today who care about you, all use deno. at least 2 hate cloudflare and I'll ask the third in an hour :)
If you find a teleporter boat, we will have dinner then at river Rhine as said https://digitalcourage.social/@sl007/114541032066943132

The comment makes me ad-hoc paste the as<->kv in a gist although it has now bugs, just as a proof that I am working https://gist.github.com/sebilasse/eb23601dd34e9e2b6916300c78a1a664
Maybe all I can do now.

Wanted to represent as much as possible in 1 byte, so made a huge change yesterday, thought I could finish, worked until 4 and drove to Duisburg 3 hours later. After dinner I will continue coding cause we intended to use fedify in the both clients which Clemens describes in the video and in mine.

For those concerned that Fedify might drop Deno support in the future: Fedify will continue to support Deno. When I mentioned considering leaving Deno, I didn't mean dropping Deno support; I meant considering using Node.js instead of Deno in Fedify's development environment. In fact, many packages that support Deno (e.g., Hono, Valibot) don't use Deno in their development environments, yet they have no problem supporting Deno. Anyway, please don't worry.