Re: new Getting Started page
Is there any reason why the 'Getting Started' shouldn't essentially follow the form: 1. Download clojure and unzip 2. Move to the folder and type 'java -cp clojure.jar clojure.main' in a terminal For the sake of testing your new page, I downloaded clooj (ugly ugly name) and ran it. On trying to create a project, the first question after specifying a project folder was: Please enter a fully-qualified namespace [ ] huh? This is hardly the kind of thing that's conducive to playing about happily discovering functional programming. Can I have multiple prompts in clooj? Can I easily pull in clojure files. Where do I specify other jars? Classpath? There's a huge set of advantages to starting in a terminal: 1. You can *see* the line that starts Clojure. If something's broken, you have a starting point. 2. You can easily add jars. 3. You can start multiple terminal windows to try different things. 4. You can use your preferred editors, anything from notepad+ up, instead of some incomplete 'IDE' [Note: without starting a project, typing in the bottom right window executed commands with the input and output sort of interleaved, but without my input shown against user=>, instead shown below it.] I'd suggest that having beginners to the language start off in a terminal typing into a REPL is absolutely the best possible thing. Packaging a jReadline would be smart too. Thanks, and I shall now go back into hibernation. Jonathan On Sep 2, 5:34 pm, Sean Corfield wrote: > I think this is a much better on ramp for folks new to Clojure and the > "bullet list" of the current "Getting Started" page really should be > the "next page" not the first one. > > > > > > > > On Fri, Sep 2, 2011 at 3:13 PM, nchurch wrote: > > There was some discussion about the Getting Started page last night at > > the Bay Area meetup. I've put together an (I think) improved version > > at > > >http://dev.clojure.org/display/doc/Getting+Started+for+Beginners > > > Any suggestions/additions/deletions? If this overall looks good, may > > I replace the current page at > > >http://dev.clojure.org/display/doc/Getting+Started > > > with this one? I'd put the current page under "other options", > > because it gives a lot of choices. > > > My hope was to give a relatively clean path for beginners (who are the > > audience for Getting Started), instead of just throwing everything > > there is at them without comment. Someone who has been around Clojure > > for a while knows that Lein is much more standard than Gradle, but to > > a reader of the current Getting Started page they look the same. -- 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
Re: Getting Clojure into the workplace, how do you do it?
On Jul 6, 11:37 am, Edmund Jackson wrote: > An exercise in declarative programming... > > On 6 Jul 2010, at 17:15, Wilson MacGyver wrote: > > > > > > > my story isn't a very interesting one. I simply told everyone on the team to > > learn it, because we are going to use it :) > > > On Tue, Jul 6, 2010 at 4:50 AM, Nick Mudge wrote: > >> One of the things I like about Clojure is it is a way to get lisp and > >> functional programming into workaday programming work; into the many > >> places and businesses that use Java. > > >> I'd be very interested to hear stories or experiences of getting > >> Clojure into the workplace and how it was done. That is, convincing > >> customers and business people and other programmers that it is okay > >> that you start doing your work in Clojure in your job. And similar > >> such experiences. > > -- > > Omnem crede diem tibi diluxisse supremum. > > > -- > > 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 > > Edmund Clojure has enormous leverage as a Perl replacement, and for many of the same reasons. Easy to install wherever there is a JVM. Comprehensive libraries that run cross-platform. Pure Java drivers for major databases. I reckon that if doing any kind of prototyping is in your job role, then anywhere you used Perl, you can now use one of the 'next wave' of languages such as Ruby, Clojure etc., where once you might have used Perl. Sorry Perl folks! Jonathan -- 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
Re: Why I have chosen not to employ clojure
On Mar 22, 1:10 am, Luc Préfontaine wrote: > An IDE becomes a necessity as the complexity of your software is > increasing. > > Now what's a complex piece of software ? > > Presently we have 12 components in production some being several > thousand lines covering three languages (Java, Ruby and Clojure). > 4 others components are in progress. Add to this that we use Spring and > a number of other frameworks for which plug ins are > available to ease the pain. > > Refactoring, code searching, configuration validation, ... are > significant features we need otherwise we would spend a lot of time > to keep things in sync, > > We started to work with Clojure in command line mode. However at a > certain moment it became clear that keeping Clojure > separate from the rest of the core was not the way to go. Today we are > mixing components from different languages/frameworks > in common Jars. Deployment is much more easier this way and using a > common IDE makes that possible. > > If the consensus is that we need to package installers to get simple > Clojure REPLs running on > Windows and Linux in a command line window then let's do it. I think > that all the infrastructure is ready (maven like repo, ...). > > Luc > > > > On Sun, 2010-03-21 at 22:52 -0500, Cosmin Stejerean wrote: > > On Sun, Mar 21, 2010 at 10:20 PM, Luc Préfontaine > > wrote: > > > Yes we could have a complete package to run Clojure from the > > shell command line but how far could someone go with this > > to build a workable system without an IDE ? > > > [...] > > > Comments anyone ? > > > I can get pretty far writing an application in Python with nothing > > more than good command line support and syntax highlighting in any > > text editor. Anything extra like completions, refactoring, etc, are > > just nice-to-haves. I don't see why an IDE is required for writing > > workable Clojure apps. > > > -- > > Cosmin Stejerean > >http://offbytwo.com > > > -- > > 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 > > > To unsubscribe from this group, send email to clojure > > +unsubscribegooglegroups.com or reply to this email with the words > > "REMOVE ME" as the subject. I've noticed there have been an increasing number of solutions to running Clojure over the last year or so, which does leave a lot more to go wrong versus the default solution of just running at the command line. If someone asked me to recommend a way to get into Clojure, I'd definitely suggest just running at the command line, and editing files with notepad or whatever. There's no real substitute for learning at least the basics of the class path and how to fix things when they go wrong. This is also the absolute simplest way to go, and in my experience, only a bad Java install (frequently on Windows) can mess it up. Even running barebones like this, it's easy to copy in Jar files for gui code, add 3rd party jars etc., whilst not having a bunch of things happening in the background. Just call me Ned Ludd! Best, Jonathan -- 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 To unsubscribe from this group, send email to clojure+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
Re: Simple functional programming lexicon?
On Mar 17, 7:28 am, Ben Armstrong wrote: > I am new to clojure and functional programming, but not to programming > in general, having been in the profession for a quarter of a century. > I'm trying to stretch myself a bit by learning clojure, but some of the > threads here go beyond mere stretching to verge on head-exploding. In > my offline reading of this list this morning, I tried using the tools > available to me at the time (dict client and a few dictionaries like > foldoc) to make sense of words like: http://foldoc.org/monad. I > survived to write this post, but only barely. > > What I would like to have is some sort of lexicon to at least help > explain the terminology in a way that doesn't require three years of > academic exposure to functional programming to read. Is there such a > reference? Or should I just ignore threads like "Why do functions in > the state monad only accept one value?" and be happy that at least > somebody cares about this stuff, so that I don't have to? > > Ben Ben, You can do a LOT with just a basic level of Clojure. I'm writing a database loader to help support an iPhone app I'm writing, and got done in just a few hours whilst only scratching the surface of what's available. No paralleism, no monads, no macros, no refs. My opinion, and it may only be valid for me, is learning a language works best when you have a definite task, and you can build code, then better code, then even better code in the language you're trying to learn. I have a couple of the books, but as yet, the best method for learning seems to be google and example code. Tim Bray has a Clojure Wide Finder series that makes interesting reading. The best thing about Clojure is the immediacy and ability to syntax check as you go. I'm using TextMate with the Clojure bundle and it's working great, just hit clover-R on hightlighted text and the result comes right back... In short don't worry about monads... The terminology is awful, and they make my head explode too. Here's a nice little piece of code that sucks in a file and inserts it into a SQL table. This is the sort of conciseness I love about Clojure. (defn load-records [table-name file-name] (doseq [line (-> file-name java.io.FileReader. java.io.BufferedReader. line-seq)] (let [fields (map #(.replace %1 "~" "") (seq (.split #"\^" (str line "~"] (sql/insert-rows table-name fields If this sucks as code, someone jump in and tell! Best Wishes, Jonathan -- 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
