4 ms·
so its basically chrome-headless with a different UI and 20% slower because it is running via an interpreted nodejs rendering that is then compiled into a binar
by jijji 9y ago
so its basically chrome-headless with a different UI and 20% slower because it is running via an interpreted nodejs rendering that is then compiled into a binary. why not just use chrome? If you're going to use an existing browser, why not use Dillo or Lynx as the backend, which really are minimalist in terms of memory usage.
- deleted 9y ago[deleted]
- AstralStorm 9y agoOr test Servo... (Mozilla's new engine.)