3 ms·
Maybe I'm missing something, but this seems like it would get unwieldy very quickly for anything more serious than toy examples. Even the toy examples I'm havi
by war1025 7y ago
Maybe I'm missing something, but this seems like it would get unwieldy very quickly for anything more serious than toy examples.
Even the toy examples I'm having trouble following along with.
The benefit of code-as-text is that you can navigate the text without knowing what you are looking for.
This seems to take the opposite approach of making it very easy to look things up assuming you know ahead of time what you are looking for.
That is something that a good usage of grep or some more sophisticated IDE integration will already take care of for you.
The only thing I could see this being potentially useful for is "notebook" style computation, where you are really only using the language to do things like structured math calculations.
What am I missing here?
- strbean 7y ago> What am I missing here? I think IDE tooling for Unison could pretty easily give you the exact same experience. Generate code from the AST, group it reasonably, and give you a view that is indistinguishable from a traditional source tree. It might be non-trivial to structure things nicely, but I think theres a good chance your generated structure would be better organized than a traditional codebase.