Why do you think they don’t struggle with input latency? Because the non blocking nature built into the browser model is so powerful and you cannot get that with threads.

▲

groundzeros2015 4 hours ago | parent | next [-]

I disagree with the premise. I cannot imagine a better latency experience than blocking loop IDEs like VS6.

Which inputs are getting latency? The keyboard? The files?

> the non blocking nature

https://youtu.be/bzkRVzciAZg?si=BuBXxHTgN0OqsAhI

▲

usrnm 4 hours ago | parent | prev [-]

Are you sure that latency-sensitive parts are written in async JS instead of having a separate UI thread (pool)? I have no idea myself, but without knowing the details it's hard to argue. Note, that browsers themselves, are usually written in languages like C++ or Rust. They run JS, but aren't written in it

	▲	pjmlp 3 hours ago \| parent \| next [-]
		Yes they are, the UI layer is mostly JS, outside the rendering and layout engines.
	▲	spwa4 4 hours ago \| parent \| prev [-]
		If you implement threads and code that reacts to an input queue (e.g. PostMessage, queue_push, mq_send, ...), you've implemented (probably a bad version of) async threads. And yes, that's exactly what Windows 1.0 did and what made it great. But God help you if you have to change the code. Async threads are a way to organize it and make it workable for humans.