It’s an interesting quandary. As evident in the discussion many hurdles and many more to come.

Despite all criticisms I would have of the Gutenberg project I have found it a more wise decision to stick with the main version of WP. I like to distinguish the block editor from Gutenberg because as a basic editor it is a pretty good replacement for the older editor.

On top of this, there is still plenty of scope to continue working in the classic way, if you want. I actually use the block editor for post content as it is pleasantly useful for this. Where I have issues is with how there is a jump to FSE before many functional workflows and responsiveness has been treated properly. One big gap for example is the lack of an interface set up just for data entry, using just custom fields and having the block editor component hidden as it is surplus to requirements in this type of workflow. Interesting how WooCommerece hasn’t yet presented us with a Gutenberg look for editing products?

Giving it full consideration I think sticking around, assessing and appraising the development with the Gutenberg project and challenging it in a critical manner is a better bet, postponing a fundamental fork to a later date. That fork should be to either adjust to WP as it is or, move to something other than WP, if such a viable option can be found.