3 ms·

I've heard people complain about parentheses, but indentation isn't usually the issue. I challenge you: I looked at your personal website, and you seem to claim

by jdale27 13y ago

I've heard people complain about parentheses, but indentation isn't usually the issue. I challenge you: I looked at your personal website, and you seem to claim experience in Java and C. Show me a large codebase in Lisp and a large codebase in Java or C where the Lisp codebase is dramatically less readable than the Java or C codebase due to indentation.

javajosh 13y ago
You seem very upset. Calm down. I just had an idea that it might be fun to represent lisp code in a treemap. Or rather a zoomable treemap like this: http://bost.ocks.org/mike/treemap/
- heretoo 13y ago
  Perhaps like these? http://foldr.org/~michaelw/emacs/ http://foldr.org/~michaelw/emacs/
  - arh68 13y ago
    I very much like the mwe-color-box.el example. Is something like that possible for backquoting? The quoting-levels would be much easier to see with nested background shading. I'll have to try it at home.
- jdale27 13y ago
  Not upset, just tired of ignorant programmers who get off on complaining, and inventing solutions to imaginary problems (bad syntax? ooh, clever visualization!) rather than actually writing code. By the way, you didn't answer the question -- how much Lisp code have you written, "javajosh"?
  - jacquesm 13y ago
    Could you lay off the personal attacks?
- arh68 13y ago
  >it might be fun to represent lisp code in a treemap Wow, yeah, that's a really interesting idea. Is there just one (good) way to map a codebase? Many? It seems like a bad idea at first glance, since the map shows, at any level, more things with less context-per-thing when compared to straight text. It seems totally natural to use it for profiling. Refactoring would be a lot more grokable if it could all be visualized at once. But how would it work for scanning/editing & digging through documentation?

3 ms·

I've heard people complain about parentheses, but indentation isn't usually the issue. I challenge you: I looked at your personal website, and you seem to claim

by jdale27 13y ago

javajosh 13y ago
You seem very upset. Calm down. I just had an idea that it might be fun to represent lisp code in a treemap. Or rather a zoomable treemap like this: http://bost.ocks.org/mike/treemap/
- heretoo 13y ago
  Perhaps like these? http://foldr.org/~michaelw/emacs/ http://foldr.org/~michaelw/emacs/
  - arh68 13y ago
    I very much like the mwe-color-box.el example. Is something like that possible for backquoting? The quoting-levels would be much easier to see with nested background shading. I'll have to try it at home.
- jdale27 13y ago
  Not upset, just tired of ignorant programmers who get off on complaining, and inventing solutions to imaginary problems (bad syntax? ooh, clever visualization!) rather than actually writing code. By the way, you didn't answer the question -- how much Lisp code have you written, "javajosh"?
  - jacquesm 13y ago
    Could you lay off the personal attacks?
- arh68 13y ago
  >it might be fun to represent lisp code in a treemap Wow, yeah, that's a really interesting idea. Is there just one (good) way to map a codebase? Many? It seems like a bad idea at first glance, since the map shows, at any level, more things with less context-per-thing when compared to straight text. It seems totally natural to use it for profiling. Refactoring would be a lot more grokable if it could all be visualized at once. But how would it work for scanning/editing & digging through documentation?