Re:Scheduling in React
by sktrdie on Thursday March 07, 2019 @02:38PM
(#19331416)
I feel that this low-level performance stuff should exist in browser-land and not in framework-land. Kudos to React for finding a good implementation though
[ Parent
| on HN ]
The Chrome dev team is working to create a scheduling API in the browser: https://github.com/spanicker/main-thread-scheduling
Re:Scheduling in React
by danabramov on Thursday March 07, 2019 @05:40PM
(#19333340)
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 ...
Re:Scheduling in React
by quickthrower2 on Thursday March 07, 2019 @03:47PM
(#19332195)
We’ll end up with threads in JS one day.
Re:Scheduling in React
by danabramov on Thursday March 07, 2019 @05:41PM
(#19333349)
Hopefully without a "Global Interpreter Lock".