On Wed, Apr 13, 2011 at 8:45 AM, Chas Emerick <cemer...@snowtide.com> wrote: > > On Apr 13, 2011, at 1:08 AM, Ken Wesson wrote: > >> Since these issues have been raised on the Enclojure Google Group by >> various people repeatedly over the last couple of years, to no effect, >> it seems that they need to be raised elsewhere to actually get the >> attention they deserve. >> >> Someone fix this in Enclojure 1.5 please! At least one of bug 1 and >> bug 2c, and preferably all of them. > > Entirely rhetorical question: if you've posted messages to the group > dedicated to the project in question, what makes you think posting to a > general-interest list will have the effect you desire?
I haven't, actually. I only noted that others have, and that the data indicated that doing so was ineffective. Hence why I haven't bothered. > One might as well hope to affect change in Clojure by posting to a > generalized JVM language list. If the Clojure list was nearly dead, getting only 2 or 3 posts a month, and inquiries and reports posted here tended to sink without a ripple, one would obviously have to go elsewhere. > Anyways…anybody can be that "someone", given sufficient interest and > motivation…even you. Not really. I don't know beans about Enclojure's internals. It would take me a lot longer to read and study and fully understand the source code, figure out what the problem is, and fix it than it should take any of Enclojure's existing developers to figure out what the problem is and fix it. -- 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
