News for hackers. Stuff that matters.
Re:What Made Lisp Different (2002) by fiddlerwoaroof on Sunday February 18, 2018 @04:39PM (#16408874)
Well, the “right” way to do it would be to make the textual representation of the syntax a view layer concern and not the format in which the code was serialized. For example, you could store everything as s-expressions or some binary representation of an AST and then have a lens that pretty prints the code with the programmers preferred syntax and the reverses the programmer’s edits to the underlying serialization format.

I suspect this would work best for an image-based smalltalk-like system where the “source of truth” would be the version of the code persisted in the image and then the textual representation would be generated from that on demand.

Re:What Made Lisp Different (2002) by fiddlerwoaroof on Sunday February 18, 2018 @07:38PM (#16409894)
A really interesting extension of this is to use lisp-style symbols instead of strings to represent variables, which would make it possible to localize the functions and keywords of your language so that a developer could collaborate in his/her preferred language.