Editor is the paramount of the ambitious goals of Roc. We would like to shift the paradigm about what is possible to do with code as a structure. Current paradigm of editing code is established in the 70's past century. While we are running machines that can render millions of triangles per second, and processing huge amount of data to render a 3d game, we are still stuck with clunky editing paradigm of machines that had monochrome displays. We have build whole set of mystical practices and rituals of converting scrolls of flat paper into a running computing machine. But we propose to build upon them the new vision of how one would interact with the code. [Insert LotR Meme, One does not simply interact with the code] We have opportunity to build the editor that has great proximity to it's compiler so the feedback loop between the developer and the machine can be extremely fast. We can setup our selves for great debugging experience if we design it and build it properly. Add to that the fact that Roc's syntax allows us some very sooooth editing experiences. Fact that is pure functional means that we can select any expression or sub-expression and test it independently. We for sure will know the types of all the constituent parts, and can show you necessary signatures or implementations. There is also opportunity to have a sound and voice based editing, which can work excellent in the case of Roc, thanks to his design choices. The vision how we would archive that is well expressed in Richard's short interview https://www.youtube.com/watch?v=ITrDd6-PbvY. TLDR; Packages would ship libraries with accompanying editor plugins, which will integrate it's specific data tools as editor plugins. Think of Regex Visualizer, Color picker and so on, shipped right with the Regex/Color library. To make such great thing possible we will need to focus on it, and giving it unfair advantage over standard methods how languages integrate with existing editors. I invite you to join us of making editing experience worth of 21st century!