Conversation

Notices

1. Embed this notice
   Baldur Bjarnason (baldur@toot.cafe)'s status on Thursday, 25-Jul-2024 00:32:40 JST Baldur Bjarnason

   in reply to

   • lj·rk

   @ljrk I suppose I should have been clearer about this: I was not talking about using Deno at all so whatever issues that runtime has are beside the point

   The deno std modules generally work in the browser and on the server. That includes node.js, bun, and cloudflare workers, not just Deno.

   I'm not a big fan of Deno itself, as I've written about earlier, but the std modules look like decent reusable bits of code that support a wide range of platforms

   • Embed this notice
     Baldur Bjarnason (baldur@toot.cafe)'s status on Thursday, 25-Jul-2024 00:32:40 JST Baldur Bjarnason

     in reply to

     • lj·rk

     @ljrk That the sandbox is broken does support my overall "don't use Deno itself" stance, though 🙂

     And the link you posted is an interesting investigation.

   • Embed this notice
     lj·rk (ljrk@todon.eu)'s status on Thursday, 25-Jul-2024 00:32:42 JST lj·rk

     in reply to

     @baldur The deno sandbox is quite badly broken though :~

     https://secfault-security.com/blog/deno.html

   • Embed this notice
     Baldur Bjarnason (baldur@toot.cafe)'s status on Thursday, 25-Jul-2024 00:32:43 JST Baldur Bjarnason

     Sudden random thought: Deno’s standard library might be JSR’s killer app.

     https://jsr.io/@std

     These modules all look decently maintained, tested, self-contained, and useful. They work both in the browser and on the server

     I still think JSR itself is kinda pointless, but I’m tempted to use it for my next personal project just for the deno std modules.