2 Comments

  1. Victor Kane
    · Reply

    Thanks so much for this brilliant conversation. Among many important things, like having to unlearn to learn, what leaps out at me is how full site editing and the block based approach itself create a separation of concerns, as Ajit Bohra pooints out, in the development team workflow itself. This is bang on the process being inside the code, and bang on the whole concept of events bubbling up and data sinking down, hydrating components, in reactive programming in general, and in React in particular. So everyone who is trying to wrap their heads around React, please, please, read and quickly work through the brilliant “Thinking in React” section right there in the React docs for a series of great “aha” moments (just to add my two cents to the list of learning resources): https://reactjs.org/docs/thinking-in-react.html

    Report

  2. Varun Pahwa
    · Reply

    The podcast was amazing and it is no doubt Gutenberg is coming up as a great editor but there are some flaws that I’ve still noticed it. For example, it is too laggy when we scroll down, the responsive modes do not work correctly, the changes sometimes don’t show up, the editor is stuck on saving a draft.

    Do we have any fixes for the above-mentioned problem as well?

    If yes, would love to hear it.

    Thanks

    Report

Leave a Reply to Victor Kane Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: