Have you heard of the Unison Codebase Manager (ucm)? In Unison ( https://www.unison-lang.org/ ) all code is stored as its AST and then you can 'chat' with ucm asking it for specific type signatures for example. Also the text you write as code really is just an intermediate representation and theoretically ucm could give you all sorts of different views on your code.
So it's Lisp with uglier syntax?
Ask HN: More “experimental” UIs for editing/writing code?
21–30 of 137 posts
Re: Ask HN: More “experimental” UIs for editing/writing code?
#22Those who cannot form a complete sentence resort to grunting and body language. When you learn to code, you'll have many fine text editors to choose from.
Formal language is certainly the most effective mode of communication for some things, but don’t discredit the value of other forms.
Also, this comment seems to discount the spirit of the post without offering any real reasons why.
Re: Ask HN: More “experimental” UIs for editing/writing code?
#23- like https://www.liquidtext.net/ for program codes ? - or Flow-based programming ? --> https://github.com/topics/dataflow-programming
It reminds me a bit of Muse https://museapp.com/
Re: Ask HN: More “experimental” UIs for editing/writing code?
#24 1948 Plugboards
1949 Keypunch
1963 Teletype
1970 VT05
1980 Symbolic Lisp
1980 Smalltalk
1986 Boxer
1987 Self
1987 HyperCard
1987 Alice Pascal
1991 Visual Basic
1991 AgentSheets
1994 SK8
1996 Squeak/eToys
2001 Eclipse
2003 Flash MX
2005 Scratch
…
https://docs.google.com/presentation/d/e/2PACX-1vSPuf3eQ2tlC...Re: Ask HN: More “experimental” UIs for editing/writing code?
#25Re: Ask HN: More “experimental” UIs for editing/writing code?
#26Have you heard of the Unison Codebase Manager (ucm)? In Unison ( https://www.unison-lang.org/ ) all code is stored as its AST and then you can 'chat' with ucm asking it for specific type signatures for example. Also the text you write as code really is just an intermediate representation and theoretically ucm could give you all sorts of different views on your code.
So it's Lisp with uglier syntax?
Re: Ask HN: More “experimental” UIs for editing/writing code?
#27What's interesting is how this forces you to think carefully about structuring your files, folders and code. It also allows you to leverage the Windows files explorer and have your code opened in multiple windows.
I'm now using VS Code. I hate how the file explorer jumps around when closing a tab (because it tries to select whatever other tab becomes visible). VS Code also doesn't allow me to easily open my files in multiple windows. Meanwhile we have browsers that allow us to freely open windows or tabs.
Re: Ask HN: More “experimental” UIs for editing/writing code?
#28Have you heard of the Unison Codebase Manager (ucm)? In Unison ( https://www.unison-lang.org/ ) all code is stored as its AST and then you can 'chat' with ucm asking it for specific type signatures for example. Also the text you write as code really is just an intermediate representation and theoretically ucm could give you all sorts of different views on your code.
Re: Ask HN: More “experimental” UIs for editing/writing code?
#29Edit: adjust autocorrect spelling choices
Re: Ask HN: More “experimental” UIs for editing/writing code?
#30Earlier quoted context omitted.
So it's Lisp with uglier syntax?
in lisp, you don't know what a given symbol means out of context (i.e. imports/macros in the environment). in unison, all functions are content-addressed so you can literally send code over the wire and dependencies are automatically resolved. it's a really cool system!