 |
| “What, you mean like we do in Servo?” (comment) | ||
| recommended by 1 user | 2015 | larsberg on: First Impressions Using React Native | concurrency | original thread | | ||
| larsberg on Feb 6, 2015 | on: First Impressions Using React Native | view on HN | ||
| One user recommended this comment. What they said: |
|
jlongster Feb 20, 2015 | on: Statements about the Mobile Web | context
I used to think Servo would just make the web a little faster, and never understood the true impact it might have until this comment: https://news.ycombinator.com/item?id=9011215 and pcwalton's response in that thread. Servo is going to completely expose the worst parts of our current web. I'm hopeful it will start influencing standards to expose sane APIs that make it easier for current engines to parallelize. |
| Also recommended by people who recommended this: | ||
| 1. | The State of JavaScript - Brendan Eich (brendaneich.github.com) | |
| recommended by 2 users | 2012 | 380 points by ryanstewart | original thread | | ||
> I think it's a very strong point that moving script code off the main thread can help achieve smooth UIs.
What, you mean like we do in Servo? https://github.com/servo/servo :-)
Our main thread (if you can call it that) just does compositing and handles dispatching UI events. Script, layout, resource loading, and the rest run concurrently in background threads.