I've been having a (friendly) argument with a friend who is an old-school
OOP programmer. He insists that you need objects to make large-scale
codebases legible and maintainable over the long run. Quite apart from
this argument's virtues or lack thereof, this made me curious -- what are
the
I'm a little past the absolute-newb stage (also came from .NET), but I
recently came upon *Programming in Clojure* by Mark McDonnell
(https://leanpub.com/programming-clojure/), and appreciated how succinct,
clear and yet (relatively) comprehensive it is. I'd recommend it highly as
a first
Take a look at Peripheral (https://github.com/xsc/peripheral). It's based
on Component and may provide some of the functionality you need.
--
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
I'm a newbie in the JVM/Clojure world, and a past user of C#/WPF. I had
similar questions for a JVM desktop application, and came upon this
interesting project: http://open-dolphin.org/dolphin_website/Home.html.
The notion here is that you mutate very simple, generic presentation models
at
