On Aug 10, 3:00 pm, Andy Fingerhut <andy_finger...@alum.wustl.edu>
wrote:
> On Aug 10, 2:19 pm, Jonathan Smith <jonathansmith...@gmail.com> wrote:
>
> > 1.) use something mutable
> > 2.) unroll all the loops (mapping is a loop)
> > 3.) try not to coerce between seq/vec/hash-map too much.
>
> > in real world, stuff like theshootoutis pretty useless, as generally
> > you'd reach for a better algorithm rather than implementing the
> > shackled, crippled, naive algorithms that the benchmark forces you to
> > implement.
>
> > (Not that they aren't useful to some extent, just that language
> > productivity and how fast you can iterate your software design in the
> > language is, IMO, a much better indicator of a good language than
> > micro benchmarking).
>
> I agree that they are useful to some extent. In the real world, you
> would use a better algorithm, but those better algorithms can be
> implemented in any language, too. As you say, a higher level language
> that lets you iterate more quickly on multiple implementations of
> different algorithms has advantages.
-snip-
An opportunity to use Clojure to iterate quickly to an implementation
that exploits all of the available cores?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
