3 ms·
I found the second example to be way less janky. I want to be able to see what I type as I type it (e.g. for spelling mistakes). Taking a second to correlate t
by lilactown 8y ago
I found the second example to be way less janky. I want to be able to see what I type as I type it (e.g. for spelling mistakes).
Taking a second to correlate that with results I am willing to accept, but if an app is janky with basic interactions I am leaving.
- danabramov 8y agoI want to emphasise both of examples are intentionally janky (even though second is less so). As the article states, it literally has a for loop that doesn’t do anything to simulate an overly expensive tree (think thousand of DOM nodes). You can see the difference between first and second approaches that way. Although both would be fast if we remove that artificial slowdown (simulating a larger app). However I also want to note that you shouldn’t base your idea of what Concurrent Mode will feel like based on an alpha version demo. It’s work in progress and we didn’t mean to imply it’s ready to be denied at face value. https://twitter.com/dan_abramov/status/1103769293479653376 https://twitter.com/dan_abramov/status/1103769293479653376