On Thursday, 20 November 2014, Michael Cohen > wrote:
>
> - There are no releases or tags on github
> Again, I didn't really know what I was doing here, and never really
> changed the approach. What do people expect, a snapshot release for
> current development, and periodic version bumps and relea
Regarding releases, the lein release function gives you good defaults for
releasing Clojure projects, it handles tagging, commit messages, and
versioning.
https://github.com/technomancy/leiningen/blob/master/doc/DEPLOY.md#releasing-simplified
has details.
--
Daniel
> On 21/11/2014, at 1:08 p
Hi Greg,
I think all of your criticisms are very valid, and I think I've seen
most of them voiced by others at various times. I wrote it in about 3
weeks in March of 2013, when I was very new to Clojure, so I'm sure I
made lots of mistakes. I was using some Java with AWS and some
Clojure, with Jam
Hi Niels,
It is true that this comparison is a bit stacked because basically
freactive only modifies the needed attributes without needing to diff the
whole structure. I'm not sure if I understand totally your other questions
- maybe you could clarify a little.
Regarding diffing - in terms of rer
I have a bunch here, on several topics: https://tbaldridge.pivotshare.com/
. Just started a series on transducers, I'll have even more by the weekend.
Timothy
On Thu, Nov 20, 2014 at 3:04 PM, Erlis Vidal wrote:
> Hi group,
>
> Someone knows if we have screencasts on how the more skilled clojuri
Good discussion, Greg. I'll add my two cents, point by point:
> * The documentation is sparse and the code is not self-documenting.
I've occasionally had some trouble in this area, but I actually do find
that it's not too hard to map from the Java AWS api directly to clojure.
For example, this c
Hi,
I have been playing around and like it so far.
I experience some behavior here where I wonder if it is intended or if I am
doing something wrong.
I have a main-page which I mount like this:
(dom/mount! root (main-page))
and which looks like this:
(defn main-page []
[...
[:div#content
Hi group,
Someone knows if we have screencasts on how the more skilled clojurian are
working? I remember few months ago we had some "pairing" sessions that were
really popular, any recording on any of those sessions?
Usually I learn better by watching/doing than reading.
(Any? channel screencas
I just wanted to say that while amazonica is also my AWS library of choice,
and I'm so glad it exists, and "running code wins", I also run into all the
same issues that Greg listed.
On Thu, Nov 20, 2014 at 12:32 PM, Greg Mitchell
wrote:
> Thanks for creating this library, Michael. Your solution
Thanks for creating this library, Michael. Your solutions for writing the
library are creative for sure, and this library has helped with developing
with AWS. However, I've been using the amazonica library to communicate
with AWS components in an enterprise-scale project for about a year now,
a
This looks pretty impressive, both in already implemented features and
performance.
I can't help but wonder though if the example chosen to compare performance
with React/ Reagent isn't stacked a bit because effectively all nodes are
rerendered all the time ? Wouldn't this effectively nullify p
On Thursday, November 20, 2014 4:40:56 AM UTC-5, Malcolm Sparks wrote:
>
> I think the best resource for learning about component is one of Stuart's
> talks: https://www.youtube.com/watch?v=13cmHf_kt-Q
>
That seems improbable. I find it far more likely that the *best* resource
will turn out to b
Sean James, yes of course there are times that it is _needed_. Agreed.
I just would never opt for using tools like declare and letfn as the _go to
tool_. I think of cyclic dependencies as less simple, harder to grok etc.
When you need it, by all means have the power to do so, but when you don't
n
On 20 November 2014 19:33, Alex Baranosky
wrote:
> Imo, that makes the let version even better. The Clojure compiler doesn't
> to allow circular dependencies, so I would consider the letfn behavior as
> "surprising" and therefore unideal.
>
It does, via declare. This is often necessary in parser
On Nov 20, 2014, at 11:33 AM, Alex Baranosky
wrote:
> Imo, that makes the let version even better. The Clojure compiler doesn't to
> allow circular dependencies, so I would consider the letfn behavior as
> "surprising" and therefore unideal.
Mutual recursion is a useful technique in some situa
Imo, that makes the let version even better. The Clojure compiler doesn't
to allow circular dependencies, so I would consider the letfn behavior as
"surprising" and therefore unideal.
On Thu, Nov 20, 2014 at 2:21 PM, Dan Girellini wrote:
> Using letfn allows the local functions to reference each
Using letfn allows the local functions to reference each other arbitrarily.
In your example, f2 can call f1 but not vice versa.
On Thu, Nov 20, 2014 at 11:08 AM, Alex Baranosky <
alexander.barano...@gmail.com> wrote:
> letfn has no value imo. It is an unwritten stylistic rule I have to never
> us
letfn has no value imo. It is an unwritten stylistic rule I have to never
use it. Why introduce a new macro syntax for something that could just as
easily be written as?:
(let [f1 (fn [] ...)
f2 (fn [] ...)]
(+ (f1) (f2)))
On Thu, Nov 20, 2014 at 12:41 PM, henry w wrote:
> I never he
I never heard of letfn before. that looks like a clear way to do what i
need.
just found this stackoverflow thread which is relevant:
http://stackoverflow.com/questions/23255798/clojure-style-defn-vs-letfn
On Thu, Nov 20, 2014 at 3:34 PM, Alex Baranosky <
alexander.barano...@gmail.com> wrote:
>
RDF and triples stores are closely related to Frame languages, although
frames can support more semantics than a triple store. Frame languages
were designed to for knowledge representation and then can be useful. To
my mind, their big advantage is that they are relatively easy and
intuitive for p
Counterclockwise, the Eclipse Clojure development tool.
Counterclockwise 0.30.0 has been released.
The previous 0.29.1 release was buggy, so I worked hard to fix things and
come with a new stable version.
Highlights:
- CCW/Standalone product based on shiny new Eclipse Mars M3
- stability fixes
-
I'd structure my app like this.
Say there's one "pages" ns with code for different webpages
pages/index is a pretty short function
pages/dashboard is a more elaborate function and has two subcomponents:
->analytics, and ->user-info
pages.analytics/->analytics
pages.user-info/->user-info
On Thu,
henry w writes:
> you have understood my arguments pretty much. again the thing that
> bothers me is that f and g are logically part of x only, but are
> visible from y and z (even if and and y are declared higher up, the
> same problem applies to their own related, private fns and x).
Then decl
ok thanks for those thoughts.
you have understood my arguments pretty much. again the thing that bothers
me is that f and g are logically part of x only, but are visible from y and
z (even if and and y are declared higher up, the same problem applies to
their own related, private fns and x).
Looks really nice, thanks for sharing!
On Thursday, 20 November 2014, Alex Baranosky
wrote:
> Hi guys,
>
> I've further refined my print.foo project, and thought I'd share the
> latest version here with you all. I get a ton of mileage out of the library
> personally and professionally using it e
Hi guys,
I've further refined my print.foo project, and thought I'd share the latest
version here with you all. I get a ton of mileage out of the library
personally and professionally using it everyday to enhance my repl-driven
development.
Here some highlights from the README (you can read a com
Hi,
With great pleasure, I'd like to announce the finalization of the program
and opening of registration for the :clojureD, Germany's Clojure conference
in Berlin.
The conference:
http://www.clojured.de/
24th Jan 2015 in Berlin
https://twitter.com/clojuredconf @clojuredconf
The program:
h
On Thursday, 20 November 2014, Hussein B. wrote:
> Hi,
>
> Lets say that you are framework creator and to use your framework, you
> defined a macro called defcontroller where the users of your framework add
> their logic.
>
> You -as framework creator- how would you load user defined source code
I think you should consider using Clojure's protocols feature rather that
code-loading.
Frameworks take control away from a developer, seeing the developer's code
as somewhat subservient to the framework. The more common approach in
Clojure applications is to provide libraries, and expect your
Hi,
Lets say that you are framework creator and to use your framework, you
defined a macro called defcontroller where the users of your framework add
their logic.
You -as framework creator- how would you load user defined source code
files and collect their defcontroller definitions?
Thanks f
Is it possible to do some sort of batch processing with the carmine library ?
So far I'm doing the following.
(defn test-data [s n]
(map (fn [i] (reverse (conj '(taoensso.carmine/set) (str i "|color") "blue")))
(range s n)))
(def data (map (fn[i] (conj (test-data i (+ i 2000))
'server.nos
Is it possible to do some batch updates with taoensso.carmine ?
So far I'm doing
(defmacro wcar* [& body] `(car/wcar server1-conn ~@body))
(defn test-data [s n]
(map (fn [i] (reverse (conj '(taoensso.carmine/set) (str i "|color")
"blue"))) (range s n)))
(def data (map (fn[i] (conj (test-data
Adding a vote for Potemkin's import-vars.
Also, I've been using Stuart's component approach for almost a year in a
half-dozen projects and it's real value is having a consistent architecture
- I find projects that don't use it are likely to invent their own ad-hoc,
informally-specified alternat
I'm not sure I understand your tidiness argument. If x uses g and f, and g
and f are private, that's plenty related enough for me to put them in the
same namespace, preferably right before x.
If f and g are meant to be private, the only reason I would see to put them
in a separate namespace is if
I guess the question is - why do the extracted functions look ugly or lack
cohesion if they still accomplish part of the task previously done by `x`?
If they are very general - you can consider moving them somewhere else and
making them public, otherwise they should stay in the same namespace, j
35 matches
Mail list logo
