• I really don’t like the entitled tone of that post. Yes, it sucks that it will be officially EOL soon-ish, but blaming the people who move on is not the way to go. But I hope it works out.

    Or maybe I’ve just lost all my fucks to give years? ago when they added node compat and pivoted away from the thing I found relatively good. I’m not a heavy user and as long as I can host my “dozens of requests per week” projects on deno.land I will stay there, but maybe it would be easier for me to just migrate those off (again).


    score 1 · canonical

    • You may be aware, but I know I had to backtrack to understand the wording in the post, but the term “EOL” as it was used in the post itself is about author’s upcoming project which I think will be a code forge or something. I tried to find out more and gave all 10% effort for it and I still don’t know what it may be.

      It’s not that EOL in your comment is a wrong term, but I wonder if the word appeared in your mind, because you saw it in the post, even if it was about something else.

      At least that short-circuited in my head.


      score 1 · canonical

    • Eh, it’s hard for me to call it entitled when he’s picking up development himself, not just complaining about it. I’m glad someone’s keeping Deno alive, even though adoption was always a problem and now the one-two punch of a fork and the removal of Node compat means that it will be even harder to find compatible libraries for Ende.

      Ironically I was recently considering moving a few of my in-progress projects from Bun to Deno because of Bun’s instability (and acquisition by Anthropic), but now I suppose I’ll just move them to Node. Node has become the Borg at this point: it assimilates its competitors’ strengths and absorbs them. (Remember io.js?)


      score 1 · canonical