MRU 0001 (Sean) is a user on retro.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Tag urself on lisp indentation style:

;; I'm afraid of passing 80 characters
(proc1
arg1 arg2
(proc2
arg1 arg2
(cond
[(foo)
(bar 'baz 'quux)]
[else
(beep boop 'bop)])))

;; Everyone has wide monitors these days anyway right?????
(proc1 arg1 arg2
(proc2 arg1 arg2 (cond [(foo) (bar 'baz 'quux)]
[else (beep boop 'bop)])))

@cwebber 80 chars is best when you want to have 2 or 3 files open at once.

@phoe I agree, which is why I tend to be very "conservative" about width

@cwebber @phoe It seems odd that we still worry about line widths when we're editing structured data like code. Why should the formatting even make it into the file?

@phoe @cwebber For something like Lisp I guess formatting helps convey the programmer's intent, but most programming languages have far more structured syntax, and their formatting rules are often far more rigid.

@freakazoid @cwebber That's why uglifiers exist for many programming languages, automatically parsing them and indenting them.

MRU 0001 (Sean) @freakazoid

@phoe @cwebber I could get behind formatting on load and de-formatting on save.

· Web · 0 · 0

@freakazoid @cwebber Sure, but now you need to invent a binary format for your source code that is *not* text. That's an obstacle.

@phoe @cwebber No more of an obstacle than inventing a concrete syntax.

@freakazoid @cwebber ...and get other people to use it in place of text. (:

@phoe @cwebber Yes I understand the chicken and egg problem at work. It's amazing how slowly programming has moved in the past 20 years.