Multi-agent framework vs Clojure concurrency

2012-02-08 Thread Jonathan Cardoso
I'm currently working with multi-agent based systems and a teacher showed 
me the benefits of using JADE framework for those kind of applications. I'm 
not sure if it's better to use a framework like this one or if it's better 
to take advantage of Clojure and its refs, agents, atoms 

How can I compare and choose between them?

-- 
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: Multi-agent framework vs Clojure concurrency

2012-02-08 Thread Colin Yates
If the answer is efficiency then I would respond prove it, i.e. produce a 
test harness that produces the expected load so you can measure 
performance.  Other factors you might consider (when choosing between any 
different technology):

 - maturity: how mature is each technology?
 - adoptability: how accessible is the technology, how effective are the 
training vehicles (books, courses, public forums/blogs etc.)
 - nice: how much do you jibe with the technology - some love Java, 
some hate it - understanding the somewhat subjective measure of 
intuitiveness is important if it is going to be used on a day to day basis
 - lastability: it is going to become unsupported before the end-of-life of 
your project (including maintenance)

in other words, you need to answer what are the risks of using technology 
X.

For me, I choose both :) - having an asynchronous message based 
architecture allows you to write services in Clojure that use all the 
Clojure goodness or in Scala which use distributed Actors etc.  Sometimes 
thinking bigger makes things simpler - instead of insisting everything is a 
shipped in a single deployable/technology why not use the right tool for 
the right job.  Sorry - getting off track there


-- 
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: Multi-agent framework vs Clojure concurrency

2012-02-08 Thread Jonathan Cardoso
Thank's Colin, that's what I've been thinking...
Maybe some mixing is a better approach, I really
enjoy concurrency programming with Clojure, but I think I need to try some
other libraries/languages (such as Scala as you mentioned, which is great
as well) to see where each one fits in my problem, maybe that would be
better.

2012/2/8 Colin Yates colin.ya...@gmail.com

 If the answer is efficiency then I would respond prove it, i.e. produce
 a test harness that produces the expected load so you can measure
 performance.  Other factors you might consider (when choosing between any
 different technology):

  - maturity: how mature is each technology?
  - adoptability: how accessible is the technology, how effective are the
 training vehicles (books, courses, public forums/blogs etc.)
  - nice: how much do you jibe with the technology - some love Java,
 some hate it - understanding the somewhat subjective measure of
 intuitiveness is important if it is going to be used on a day to day basis
  - lastability: it is going to become unsupported before the end-of-life
 of your project (including maintenance)

 in other words, you need to answer what are the risks of using technology
 X.

 For me, I choose both :) - having an asynchronous message based
 architecture allows you to write services in Clojure that use all the
 Clojure goodness or in Scala which use distributed Actors etc.  Sometimes
 thinking bigger makes things simpler - instead of insisting everything is a
 shipped in a single deployable/technology why not use the right tool for
 the right job.  Sorry - getting off track there


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