I'm a very much a newbie to forth.

Blocks instead of files – good/bad? Agree about good idea on embedded platform. I think the case for bad appears more obvious at the moment, games are a possible case were it might be good, assets often packed into one file, could imagine block style system used during dev rather than packing the files together at end.If there was a way to mount the block file into the file system, this could allow use of external tools, probably would take many of the advantages away, need to use standard formats, be a lot of work for read/write. I see the custom editor as being one of the possible big advantages. With projects having more data types that just source code. The editor could provide a powerful unified experience with less context switching. For example changes modes on block type, spreadsheet for table data, pixel editor for art, etc.. The Cannon Cat mentioned early looks extremely interesting, good quote. Other possible advantages that come to mind 1)simplify io: less reliance on system io interface )offsets could be used directly in code 2)macro's at different part of dev cycle, e.g. thinking colorforth self modifying magenta variables 3)reduce naming pressure with blocks being numbered. The position of block could convey meaning 4)No separate packing resource files step. Blocks as virtual memory - good/bad? Hard to imagine where this be better than some sort of heap. Blocks for storing source code – good/bad? There may be something here. I think it may have to do with cogitative load. Seeing all of a related section of code together, might make it easier to see links, factoring opportunities, bugs, interface without becoming overloaded. I think this may be partly why we still have pages in digital books and websites. Code would have to be horizontally formatted. How big to make a block? One screen of text? How big the screen? My idea would be put each word definition on it own line in horizontally format. The line is as long as necessary, may need to scroll.