Too much unnecessary updates when a child element is moved to the front

**Do you want to request a *feature* or report a *bug*?** Not sure if it's a bug or an 'accepted' behavior. But this can affect performance in some situations or even 'break the expectations' in others (e.g. animating moved elements [i.e. simple moves]) **What is the current behavior?** When a child element moves from the end of the list to the front React actually moves all the other elements after the moved/last element instead of simply inserting the moved element at the front of the list. This also can be stated more generally for an element or a block of elements moving backward with a significant shift. **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).** Here is a [demo](https://codesandbox.io/s/wjZkrGVzJ) that shows the DOM operations performed on DOM nodes (moves & insertions) during reconciliation. To reproduce the issue - type '0123456789x' in the input field then click `Patch!` - now type 'x0123456789' (move the last 'x' to the front) then click `Patch!` again Here's the output  Instead of moving the 'x' to the front. React actually moves all the other elements after the 'x' *Note: the demo uses MutationObserver api to find out the operations. But you can also verify this behavior directly by commenting out the code that activates the dom observer (in componentDidMount) and watch the dom operations manually in the devtools element inspector* **What is the expected behavior?** React should perform the minimal number of operations. I know that the 'minimum' will vary for each situation and not trivial to infer for the general case. But for some common cases like this one it should be feasible. For info this use case is handled in most of the other virtual dom libs like preact, snabbdom. Inferno is a r…