Content pfp
Content
@
0 reply
0 recast
2 reactions

‍‍ pfp
‍‍
@git
Node.js is not going anywhere & will continue to rise what's going to happen is general runtimes (node/bun/deno) will converge & basically all support all the features and we'll see more & more hyper-specialized JS runtimes that are designed to do one thing/platform and do it it extremely well see reply for examples
3 replies
1 recast
8 reactions

‍‍ pfp
‍‍
@git
LLRT: serverless github.com/awslabs/llrt JerryScript: IoT github.com/jerryscript-project/jerryscript Hermes JS (engine): React Native github.com/facebook/hermes workerd: Cloudflare Workers github.com/cloudflare/workerd
0 reply
0 recast
4 reactions

Rafi pfp
Rafi
@rafi
I live in this future today. For upcoming frame.town I'm using 3 runtimes run on cloud/metal duo: deno for backend (thanks to it's exceptional devex), node for frontend (as frontend tools work well only there), and bun (for running untrusted user code and it's low resource utilization ~40% less than deno. I aimed to use only one runtime to simplify the whole stack but after much tinkering I decided that this setup makes sense, mostly because all these runtimes are interoperable with each other.
3 replies
0 recast
1 reaction

ewan (Σ, 🏁) pfp
ewan (Σ, 🏁)
@lordewan
absolutely. it's quite debatable, but so far, there's no strong reason for node.js to be replaced
0 reply
0 recast
0 reaction