Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @hboon@mastodon.social
Chee Aun 🤔@cheeaun@mastodon.social (2026-10-10 14:43:58)
@hboon yeah, mainly to diversify as Deno was built to be a "do-over" of Node.js (creator of Deno is also creator of Node.js 🤣). It uses more existing web standard APIs instead of reinventing the wheel. Though historically (io.js days), Node.js will usually slowly absorb all these learnings in later versions.
I also have two apps deployed on Deno Deploy, which I think is mainly simpler "wrappers" around CloudFlare workers/KV/etc:
- https://github.com/cheeaun/translang-api
- https://github.com/cheeaun/img-alt-api
---Reply---
Hwee-Boon Yar@hboon@mastodon.social (2026-10-11 12:39:16)
@cheeaun since you are on it. How about bun for you? I have only been using bun (because originally it was really much faster to start up and memory efficient compare to Node.js) as a dev replacement for Node.js, but not in prod because of leaks.
Reply
---Replies---
Chee Aun 🤔@cheeaun@mastodon.social (2026-10-11 13:08:12)
@hboon tried bun since the earlier versions. Now it's so "all-in-one" that it's very convenient but also too much/scary at the same time 🤣
Node is still the best "default", especially the starting point for first-time setup & external contributions. I don't see much perf/memory issues on my side, so there's no reason for me to use Bun for dev. And then Vite/Vue/Nuxt folks are more inclined towards pnpm, so all these feel more like a "preference" thing now.