Look, your IDE won't be a good clojure environment, because it will encourage sloppy thinking. Write some more macros, and learn to appreciate that you are building data structures. Really.
Grrrr.... On Dec 18, 9:37 pm, Anniepoo <annie6...@yahoo.com> wrote: > I read this and think of Roedy Green's essay on source code in > database,http://mindprod.com/project/scid.htmland on Knuth's > 'literate programming' - the idea that source code is inherently not > it's representation (it's the reader output that's homoiconic, not the > file representation on disk) and that there might be several > representations. > Reading Roedy Green's essay I think of how obsolete it sounds after > refactoring IDE's came around. Let me suggest that this is a great > idea, but one that should be part of some clojure-centric IDE, not a > part of the language. > > It seems barking up the wrong tree to think that clojure will find > more acceptance if we find some method of reducing the number of > parens involved. > What's hostile to most programmers is that Clojure demands a lot more > thinking per line of code. I remember when OO came in, and then when > design patterns came in - each decreased the amount of thinking about > code and increased the amount of typing. > After all, the same java programmers who are frightened by Clojure are > happily reading nested structures in XML all the time. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
