Hmm, IDK. I can see that it could be a good way to represent and manipulate the chunks of text once you've got them, but having to click a special icon and choose the block type every time you add a new paragraph (rather than just pressing "return" for the most common case of a new text paragraph) seems pretty clumsy.
I currently work on a site that uses TinyMCE and inserting images, videos etc. is a nightmare. There's this combination of the burden of HTML sanitization and the illusion of total freedom that TinyMCE gives to content creators. Something with better separation of content types would be wonderful.
Direct editing is becoming more common and therby acceptable I think.
We also use a similar block (or widgets) approach for our editor, and it works really well for mixing all kinds of content in one editor.
Storing them as JSON objects with client-side classes that know how to render them also makes it really easy to add or extend the widgets later on.
I've seen this idea in the real word, and it fails with editors. If you provide WYSIWYG, editors expect to format content just like one does in Word or InDesign, absolutely positioning elements, and the result to be identical (which is obviously a problem nowadays with elastic layouts and mobile sites).
At least in the example, there did not seem to be a way to undo things. This is a bit annoying, especially because it forces a confirmation step when deleting things. I think most common use-cases would be much better served by being able to undo a delete than having to confirm it each time. Even if you don't want to have a general undo button, I would prefer a GMail-style undo link that only pops up after you've deleted something to the current behavior.