Dennis Haupt <d.haup...@googlemail.com> writes: > i wouldn't suggest using a language no one has experience in at the > start of a new project. you'll mess up the core design and everyone will > course you for decades.
You are going to mess up the core design 99 times out of 100 anyways, so I don't see this as a stopper. If you get it right first go, then god bless ya. You get cursed either way, get over it, gotta pay the cost to be the boss. Hmm, nearly all the still-living projects I've ever worked on have been in languages that few if any on the team had real experience with at the start. ObjC/WebObjects, then Common Lisp, then Java, then Ruby, and now Clojure. That's mostly web apps, but also a programmable multi-agent modeling environment. All of them are still alive, tho some are 10+ yrs old, and have had nearly all bits rewritten at some point. Using the new tool/language was often the reason we were able to make those projects work, you know, so that there was someone getting paid to work on it later, who could curse us. -- Craig Brozefsky <cr...@red-bean.com> Premature reification is the root of all evil -- 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
