In reply to Greg Schoppe.

@John

That is, of course, your choice. However, keep in mind that Gutenberg is currently a plugin, and is registered and included differently than it may be post-merge. "Disable Gutenberg" currently removes the actions and filters that the Gutenberg plugin uses to install itself, but that will probably be ineffective against the merged version of Gutenberg.

So, if you use Disable Gutenberg, you have to trust a third-party developer to update their code to properly remove Gutenberg, before the 5.0 release.

Classic Editor, on the other hand, is the official tool to remove Gutenberg, and is being actively supported by the WordPress Gutenberg team. So you know it will work before the 5.0 release.