2 ms·
Deno is awesome but I'm not satisfied with implementation. I wrote very simple web server which listens for GitHub CI notifications (with deno I implemented it
by vbezhenar 4y ago
Deno is awesome but I'm not satisfied with implementation. I wrote very simple web server which listens for GitHub CI notifications (with deno I implemented it all including crypto with 0 dependencies, wow). We're tiny company so notifications are like once an hour or something like that. It eats like 50 MB of RAM and eats like 6m CPU all the time. Simple Go server eats around 20-30 MB of RAM and eats < 1m CPU all the time. I just don't understand what does deno do all the time with its 6m idle CPU. Hopefully it'll be improved in the future.
Also I think this whole granular access thing is weird. I never wanted it, container isolation is more than enough. Hopefully it does not add much drag to deno progress.
- lytedev 4y agoDeno packs a lot in and V8 is pretty big to begin with. It makes sense to me that a Go binary will be leaner in pretty much every metric than a Deno script. I think the win with Deno is the JS ecosystem and the situations where JSs dynamicity is an advantage. Sometimes (often times, in my own estimates) that's worth double the memory usage and 20% the raw CPU performance.