洪 民憙 (Hong Minhee) :nonbinary:
@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee) :nonbinary:

Anyway, the moment I heard the news, I opened an issue in Fedify with a master plan for moving Deno out of our main development tooling.

Fedify will keep supporting Deno alongside Node.js, and keep publishing packages to JSR alongside npm. Deno just won't be what we develop with anymore.

https://github.com/fedify-dev/fedify/issues/1281

github.com

Move development tooling off Deno while preserving Deno and JSR support · Issue #1281 · fedify-dev/fedify

Background Deno has announced that its team is joining Cloudflare. The Deno team will provide monthly bug fixes and security updates for the runtime for another year, then end its own runtime devel...

1 reply

Sebastian Lasse
@sl007@digitalcourage.social · Reply to 洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee
it will mean the end of our server for menschys, taxiteam, redaktor and Public Spaces then. sad :_(

Wouldn't it be an option to join a Collective first and see how we can counter this JS-Runtime-Nightmare?
digitalcourage.social/@jakeham also given that bun is now anthropic and that we created so much fediverse tooling like fedigeo, OSM and wikidata/wikipedia/wikibase Integration.

@clemensg FYI
[de] Der post oben bedeutet sonst das Ende unseres Servers.

hachyderm.io

digitalcourage.social

Jake Hamilton
@jakehamilton@hachyderm.io · Reply to Jake Hamilton

This is one of many posts I've had kicking around in my head for a while. I could have made it much longer, but I think right now the important thing is to just say the important parts and move forward. Otherwise I don't know that I would ever end up saying something at all.