On Tue, Mar 31, 2009 at 8:17 PM, Laurent PETIT <laurent.pe...@gmail.com>wrote:
> Yes, you're certainly right, but I'm only 35 old, and I don't want to yet > let my dreams behind me, given that I will certainly (I hope so!) play at > least 35 more years in this industry :-) > > I was thinking about an approach that would leverage the kind of separation > one can find in the industry such as GUI stuff in one file, backend stuff in > another, but maybe reconciled thanks to judicious use of higher order > functions and conscienscious application of macros. > > Something that can be thought of as "workable specs" for the GUI, where one > does not have to switch language from one abstraction level to the other. > I guess we are being warned about some kind of hunt for perpetual motion or "cold fusion" (maybe I can't use that analogy now - http://www.newscientist.com/article/dn16820) ... but this doesn't seem that far fetched. Instead of looking up the docs while you make an application. write the GUI code how you would want it to work .... and then fix the errors until it is legal code with the desired result. Then person b tries to use it, and proposes some tweaks that work for the new app and the original app (or shows how to tweak the original app). etc. (in theory) --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
