3 ms·
Deno 2 with full Node compatibility is huge, presupposed it works reliably without runtime surprises. I wouldn't mind if I get a warning when a Node package is
by WuxiFingerHold 2y ago
Deno 2 with full Node compatibility is huge, presupposed it works reliably without runtime surprises. I wouldn't mind if I get a warning when a Node package is not supported, but runtime must be rock solid, especially with server packages like node-postgres (pg).
Apart from this little doubt, I love it:
The APIs and std lib are so extensive that we don't need huge amounts of third party packages. Typescript support is great. Deno actually can check Typescript (not just run it by stripping it as Node or Bun). Compiling (bundling) is another great feature.
- tmikaeld 2y agoI just tested it with ioredis node.js package for production use and Deno 2 could handle: - Automatic connection pooling - 400MB/s+ of throughput - 20 000+ keys and larger values (10-50kb) - 1000+ concurrent reads/writes - 200-250MB of RAM usage max Without breaking a sweat, the limitation was my keydb test server.
- rnmkr 2y agoMaking their stdlib compatible for other runtimes are huge W! I'd drop some third party libs in favor of them.
- culi 2y agoDeno has had full node compatibility for a while hasn't it? It's very mature in my experience