Perhaps a bit too specialised, but there is a good example for
hadoopers here:
https://groups.google.com/forum/?fromgroups=#!topic/cascading-user/i3b4KZsusVg
Paco Nathan rewrote the CoPA examples from his cascading work in Cascalog.
cheers,
Bruce
--
@otfrom | CTO & co-founder @MastodonC | mastod
I think it depends a lot on your audience. For example, java spring
programmers are likely going to be impressed by the simplicity and speed at
which you can get a project started, especially when using lein and being
able to avoid the common load of bolerplate java, xml, etc. Programmers
famil
On Wed, Jan 16, 2013 at 4:08 PM, Thomas wrote:
> Hi All,
>
> Something that came up last night in the blank? thread. What is a good way
> to show someone the advantages of Clojure. Something that is simple, not
> too complicated, easily understood, shows a (significant) benefit, etc.
>
> Any idea
On Jan 17, 2013, at 7:30 PM, Mikera wrote:
>
> I'd just do it with examples at a REPL to show off different features,
> introducing them slowly, with a focus on functions and data. Examples:
FWIW I introduce Clojure to students (many of whom have no experience with Lisp
and/or Java) with the l
On Wednesday, 16 January 2013 23:08:41 UTC+8, Thomas wrote:
> Hi All,
>
> Something that came up last night in the blank? thread. What is a good way
> to show someone the advantages of Clojure. Something that is simple, not
> too complicated, easily understood, shows a (significant) benefit, etc
Here's a quick example of getting all the streets in Baltimore from a 1GB
XML file of Maryland map data. I shudder to think of how to do this in
java. Takes about 60 seconds to run on my box.
https://gist.github.com/4548456
On Wednesday, January 16, 2013 10:08:41 AM UTC-5, Thomas wrote:
>
>
I have trouble finding a simple example, but I know I have written a
lot of apps that have less than 200 lines of code, but if I had
written them in PHP, they would have been a mess.
And consider this: I worked at WineSpectator.com for awhile, and they
had me writing big import scripts for the dat
How about Clojure's web
1. Plain Clojure function as handler, request and response are just
maps, they are printable.
2. Easy testable: handler is a function, pass a request, get the
response, assert the response is wanted.
3. Easy mockable: use bindings to mock centain functions
How about something from the world of concurrency? It is not as easy to
demonstrate, though. Many true advantages are too subtle for elevatorspeak,
though. For example, people used to pitch *pmap* that way: instantly turn a
sequence transformation into a multicore-saturating performance king. Th
Hi,
I based a recent presentation in a local user group on the bank account
example: two accounts, deposit, withdrawal, transfer. Starting with maps.
Building the code. Noticing that no locks are required. Replacing maps with
records w/o changes to underlying code. Easily testing pure functions
Hi All,
Something that came up last night in the blank? thread. What is a good way
to show someone the advantages of Clojure. Something that is simple, not
too complicated, easily understood, shows a (significant) benefit, etc.
Any ideas? (As said in the other thread, I have used the blank? exa
11 matches
Mail list logo
