I would pay $20 per project for this easily. You did some great work (from the looks of it anyways) and you should get the financial reward from it. This isn't a charity, it's a service, and I would treat it as such. Keep up the awesome!

--
Cheers,

Aaron Bedra
--
Clojure/core
http://clojure.com



On 04/19/2011 01:10 PM, rob levy wrote:
This seems great. The $20 bothers me, not because I don't want to pay it, I would gladly donate this meager amount for such a useful resource. There's just something in poor taste about not making this open to everyone. And there's an implicit camaraderie and good will that developer communities have come to expect that makes this paywall seem weird and unwelcoming. If you framed this as a donation, with access not contingent on donation, it would be perfectly fine-- and people might actually use it.

On Tue, Apr 19, 2011 at 12:45 PM, Paul deGrandis <paul.degran...@gmail.com <mailto:paul.degran...@gmail.com>> wrote:

    This is a great piece visualization for Clojure and very much how I
    think about the language as I'm working with it (based on the pictures
    and descriptions).  This is a nice niche piece of documentation for
    the community, power users, and newly emerging Clojure shops.

    Is your freemium model limiting namespaces/content. functionality, or
    both?

    Paul


    On Apr 19, 9:27 am, Ambrose Bonnaire-Sergeant
    <abonnaireserge...@gmail.com <mailto:abonnaireserge...@gmail.com>>
    wrote:
    > Oh wow, this looks exciting! Subbed.
    >
    > Ambrose
    >
    > On Wed, Apr 20, 2011 at 12:19 AM, Chas Emerick
    <cemer...@snowtide.com <mailto:cemer...@snowtide.com>>wrote:
    >
    >
    >
    >
    >
    >
    >
    > > Today, I’m opening up a “preview” site for Clojure Atlas [1],
    a new side
    > > project of mine that I’m particularly excited about.
    >
    > > Clojure Atlas is an experiment in visualizing a programming
    language and
    > > its standard library.  I’ve long been frustrated with the
    limitations of
    > > text in programming, and this is my attempt to do something
    about it.  From
    > > the site:
    >
    > > While Clojure Atlas has a number of *raisons d’être*, it
    fundamentally
    > > exists because I’ve consistently thought that typical
    programming language
    > > and API references – being, in general, walls of text and
    alphabetized links
    > > – are really poor at conveying the most important information:
    not the
    > > minutiae of function signatures and class hierarchies, but the
    stuff that’s
    > > “between the lines”, the context and interrelationships
    between such things
    > > that too often are only discovered and internalized by bumping
    into them in
    > > the course of programming. This is especially true if we’re
    learning a
    > > language and its libraries (really, a never-ending process
    given the march
    > > of progress), and what’s standing in our way is not, for
    example, being able
    > > to easily access the documentation or signature for a
    particular known
    > > function, but *discovering* the mere existence of a
    previously-unknown
    > > function that is perfect for our needs at a given moment.
    >
    > > This is just a preview – all sizzle and no steak, as it were.
     I’m working
    > > away at the ontology that drives the visualization and user
    experience, but
    > > I want to get some more early (quiet) feedback from a few
    folks to make sure
    > > I’m not committing egregious sins in various ways before
    throwing open the
    > > doors to the world.
    >
    > > In the meantime, if you’re really interested, follow
    @ClojureAtlas [2],
    > > and/or sign up for email updates [3] on the site.
    > > - Chas
    >
    > > [1]http://clojureatlas.com
    > > [2]http://twitter.com/ClojureAtlas
    > > [3]http://clojureatlas.com/subscribe
    >
    > > P.S. This is a ML repost of my announcement @
    > >http://cemerick.com/2011/04/19/clojure-atlas-preview/
    >
    > > --
    > > 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
    <mailto: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
    <mailto:clojure%2bunsubscr...@googlegroups.com>
    > > For more options, visit this group at
    > >http://groups.google.com/group/clojure?hl=en

    --
    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
    <mailto: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
    <mailto:clojure%2bunsubscr...@googlegroups.com>
    For more options, visit this group at
    http://groups.google.com/group/clojure?hl=en


--
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


--
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

Reply via email to