Updated ReactDOM.hydrate() documentation to explain the React 16 behavior. Please take note! https://reactjs.org/docs/react-dom.html#hydrate …pic.twitter.com/1D5mcI75ND
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
What's your use case? Patching up can also hide other differences like wrong event listeners/state, so not necessarily just better because.
Event listeners shouldn't run in server mode, right? I don't understand what you mean by use case...
Isn't it just an abstraction leak if you wind up with different DOM based on whether you SSRed or not? I can give examples but they seem obv
My argument is that you can end up with abstraction leak regardless if you patch up the attributes or not.
So you'd need a use case where that happens significantly more frequently with attributes, and patching them up is a satisfactory fix.
Intl is only one area of different strings between browsers. Date.prototype.toString() is another, and the Web Platform above it has tons
I think we should work towards minimizing *unmotivated* differences, but the only way to wipe out Intl differences is to not have the lib.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.