On Tue, Nov 18, 2008 at 9:42 AM, Raffael Cavallaro < [EMAIL PROTECTED]> wrote:
> > > > On Nov 18, 1:46 am, "Cosmin Stejerean" <[EMAIL PROTECTED]> wrote: > > > What kind of bugs are acceptable for the > > purpose of a known good combination? Is slime starting up sufficient? > > It's a whole lot better than slime *not* starting up. Again, context: > "Getting Started." > > BTW, it's this sort of thinking, that one wants to constantly update > because some bug or other may have been fixed in the latest svn/cvs > commit that leads to projects never making releases, which is a Bad > Thing(TM). > > > > > Assuming some automated tests can be created to define the > characteristics > > of a known good combination I'll volunteer to create a continuous > > integration server to report the status of trying to use the latest > version > > of each project so interested users can quickly see if the most recent > > combination works, and if not look, at the history to find the most > recent > > one that does. Is providing automated tests something you'd like to help > > with? > > > Again, *not* looking for the latest and greatest in the context of > "Getting Started." Merely looking for "known to work even though it's > 6 months old." > > As the old chestnut goes, one never gets a second chance to make a > first impression. The first impression one gets now does *not* reflect > the quality of clojure at this point. The first impression one gets > now is "OK, broken, check back later." Clojure is more mature than > this, and the initial setup brokenness is easily solved by putting up > an archive of working versions of the various components even if they > grow to be many months old before they're refreshed. This would not > require an automated testing server, just a single tar command line > once or twice a year. > > regards, > > The complexity here lies on the Emacs/Swank/Slime side, and the coordination it requires with a matching Clojure. You can always grab the latest Clojure from svn, run ant, and have a working Repl with java -jar clojure.jar in under 30 seconds. Might I suggest that for "Getting Started", Swank/Slime is a bit much? For many people, this will be their first use of Emacs. Perhaps some simple instructions for getting clojure-mode going would be better? Its functionality/complexity ratio seems much higher. Also, I'd like not to imply that emacs+swank/slime is the only way, or a prerequisite for using Clojure. There's a mode for vim, and there's also enclojure, something for TextMate, etc. Let's not make getting started any harder than it need be. People can move up to swank/slime when they are ready. Rich --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
