Hacker News Reader

The Chrome dev team is working to create a scheduling API in the browser: https://github.com/spanicker/main-thread-scheduling

Yep, and React is actively collaborating with them.

Or maybe not even in the browser but in the OS?

It is interesting how we build a new layer on top, and then notice that we need to reproduce all the functionality of the lower levels.

Maybe Open Implementation wasn't such a bad idea?

Yes it's highly unsatisfactory that frameworks are implementing "threads" (i.e., fibers) now, while the OS already provides native threads.

Perhaps it would not have been so bad if they just kept the interface the same ...

We’ll end up with threads in JS one day.

Hopefully without a "Global Interpreter Lock".

I would prefer that they implement it in the same way go has with channels.