5 Comments

  1. Anh Tran

    This is a great discussion. I’m following the debate and will choose whatever the core team selects, just like other people. While learning other frameworks is doable, we don’t want to waste our resources on things other than what will benefit most.

    Report

    • Matt

      Well said! I totally agree. I’ll be doing the same. Your metabox.io plugins are awesome. Thanks so much for making them and keeping them all going. :-)

      Report

    • Jon

      I keep seeing that sentiment echoed and I mentioned it several times during the discussion. There is a disconnect between what the WordPress team wants ideally, everyone to use whatever framework they want, and what people actually tend to do.

      Report

      • Gary

        I wouldn’t say that there’s a disconnect, I think it’s easy to get the impression that everyone will use the same framework as Core based on comments on the Tavern or in core-js chats, but I don’t believe that’ll be the case when the wider WordPress world starts building Gutenblocks.

        It’s also worth noting that, even if you do use the same framework at Gutenberg, you’ll still have the same API available as if you used any other framework. Framework-specific functionality is intentionally not being exposed, which gives us the freedom to switch the framework in the future, if need be. Relying on any framework internals is absolutely not recommended, as framework maintainers generally don’t maintain backward compatibility with their internals, and we certainly wouldn’t be able to in the event of a framework switch.

        Report

  2. Mabuto Bonzana

    I would still recommend building it with Laravel.

    Report

Comments are closed.

%d bloggers like this: