5 ms·

I was hoping this would be a story about native react-style rendering within the browser engine itself, something I've been waiting for since virtual DOMs first

• dustingetz 11y ago
  I still remember your Conj talk in 2012 about virtual dom, 6 months before react was announced. Where did you first get the idea?
• daxfohl 11y ago
  I was hoping it would be a story about injecting links/buttons for each possible state transition on a page, that would cause a full browser refresh from the server.
  • firasd 11y ago
    Not quite sure what you mean? If you turn off JavaScript in the example app you do get something like that—the links reload the browser page, and the comment form submits the comment, then renders the new state of comments (just by processing the comment on the form submit and then re-directing you back to the page.)
    • daxfohl 11y ago
      Something more universal (albeit less useful). i.e. something that automatically checks your rendered DOM for every possible Redux state transition, creates a callback URL for it, and sticks a link for that at the bottom of the page. Essentially, distributed redux: if redux is (state, action) -> state, then that over HTTP.
• smadge 11y ago
  I feel like the problem being solved by React and other virtual DOMs are only relevant because user agents never bothered to solve janky page transitions. Couldn't browsers do a minimal DOM update themselves without losing context or introducing weird flashes? Is this what you mean by "react-style rendering within the browser engine itself"