V8

Raised as a usability problem by 9 people on Hacker News over 9 years (2012–2020), in 9 threads.

People raised many different problems with V8, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 9 complaints

Tracing what the V8 JIT does has an awful workflow2020-03-29
Can't get a result back from vm.run* when async calls are needed2019-09-24
Page is hard to read on mobile, freezes, and redirects when zooming out2018-02-01
Must load files one by one to find the right compiler output version2017-08-21
Must avoid language features like try/catch to keep code fast2017-05-16
Optimization tracing doesn't explain why code is deoptimized or stays slow2017-03-02
Embedding interface is painful to work with, pushing author to switch engines2014-03-24
Engine internals and debugging tools are barely documented, and docs go stale as things change2013-08-19
Always prints large arrays in full, hanging V8 when a large array is a local variable2012-01-26