(Source: I wrote the REST API in WordPress and lead the API team for many years.)
But instead let's force feed - oops, I mean ship - and bake in a product (i.e., GB) that was half-baked technology implementation and barely an afterthought in terms of user experience. (Note: UX in this case includes all the devs who were begged to jump on board, and then jerked around like a puppy on the leash.)
WP core should be a service. Lean, tight and clean. Tightly coupling more and more likely unnecessary features to that doesn't help anyone. Trying to maintain that monolith is overly complicated. And so on.
We have the plugin architecture. If it's broken, then let's fix it. If it needs some sort of dependency manager, then let's talk about thst as well.
But Gutenberg? That makes 2020 look like a summer holiday, and we all know how bad 2020 has been :)
WordPress should not have the same mindset as Jetpack. Oops? Did I just say that?? ;)
But more importantly, it should not be in core. Full stop. Once WP became REST-driven the push should have been to lighten core. That is to decouple as muxh as possible. Core is that _core_. Then you configure your needs from there. Core should be the basics, as light and as lean as possible.
But instead, more and more unnecessary bloat. More and more features with less and less benefit.
Yes, I'm looking at CraftCMS and others as well. WP has jumped the shark. It's not going away. But I'm tired of having to shower after everytime I work with it.