You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The primary source of memory usage is the typescript compiler, which deno runs to provide auto completions for the REPL. This is the same way that deno's LSP provides completions to editors. I'm not sure about python, but node dynamically searches prototypes at runtime to provide completions (which is much less intensive than running TSC for type information).
The more fair comparison would be how much memory it takes to run an empty file.
docker run -it --rm denoland/deno:2.1.5 repl
150MB from
docker container stats
:For reference, I observed the following for other container images:
docker run -it --rm python:3.12 python
: 11MBdocker run -it --rm node:22 node
: 11MBThe text was updated successfully, but these errors were encountered: