Performace was an issue right from the start for this project, that's
why I went down the protocol/record path instead of
multi-methods...surely, this is a decision to be made in the beginning,
isn't it?
I did take into account all the comments so far...my world is now fully
immutable, reset! is out of 'move', and I've got far less macros
(replaced them with return-type-hinted fns)...
Also I only starting optimizing (type-hinting) when the namespace
finished...ok, I did have some design error as it turned out, but it was
only when I had no more code to write in that namespace that I started
type-hinting...
I appreciate your concerns though... :-)
Jim
On 15/06/12 12:41, Korny Sietsma wrote:
You keep talking about performance. I'm a long way from being a
clojure expert, but one thing I *do* know is that premature
optimization is the root of many many evils.
May I suggest you first get your app working, in a clean
understandable fashion, ideally with some solid unit tests. Then, and
only then, profile it, work out if it performs adequately, and
optimise the parts that need it?
(apologies if this is the approach you are already taking - it's bit
clear from your posts if that is the case)
- Korny
--
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
