Re: [ANN] Cryogen - Static Site Generator

[Ryan McGowan]

Pretty cool. I'll have to compare it with incise 
 in detail later.

On Thursday, November 13, 2014 1:27:44 PM UTC-8, Carmen La wrote:
>
> Check out my first project! As the title says, it's a static site 
> generator :)
>
> Blog post: http://carmenla.me/blog/posts/12-11-2014-post1.html
> Github repo: https://github.com/lacarmen/cryogen
>
> Any feedback is appreciated :)
>

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Thnx for clojureconj videos !!

[Colin Fleming]

Absolutely, the team did a really amazing job getting them up so quickly.
This was surprisingly useful even being at the conference - I missed a few
talks due to hallway track conversations, but I could still see them on the
videos in time to talk to the speakers about them. Really great job.

Cheers,
Colin

On 22 November 2014 at 08:09, Geraldo Lopes de Souza 
wrote:

> Thank you very much for clojureconj videos !!
>
>  --
> 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 unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: lein repl timeout

[Colin Fleming]

Hi Neil,

This looks like an issue a user had with Cursive a while ago, which I never
totally got to the bottom of. See
https://groups.google.com/d/topic/clojure-tools/lmjCX3AjAfE/discussion and
the associated GitHub issue. In particular, guns wrote a really useful mail
which for some reason doesn't appear in the Google groups thread, but you
can see it in my reply here:
https://groups.google.com/d/msg/clojure-tools/lmjCX3AjAfE/PV7W_-oefVYJ

Cheers,
Colin


On 22 November 2014 at 20:23, Neil Laurance  wrote:

> Hi there. Hope someone can help me with an issue I am having with lein
> repl. I did post on StackOverflow
> 
> as well, but no luck there yet.
>
> I have been using lein from my home Mac for quite some time, but hadn't
> started a repl for a couple of days.
>
> When I came back to use lein repl again, it now fails with a timeout.
>
> *Based on a hunch from another post, I managed to find a workaround of
> turning off my wifi which seems to resolve things ?!?*
>
> But if anyone can help me with a better solution, that would be
> appreciated.
>
> The lein version I am using is: Leiningen 2.5.0 on Java 1.7.0_11 Java
> HotSpot(TM) 64-Bit Server VM
>
> I took a thread dump
> , which showed
> 'Thread-4' attempting to make a socket connection.
>
> "Thread-4" prio=5 tid=0x7ffb6a0a nid=0x2707 runnable 
> [0x000114aa8000]
>  java.lang.Thread.State: RUNNABLE
>  at java.net.PlainSocketImpl.socketConnect(Native Method)
>  at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
>  - locked <0x0007f80aa8a8> (a java.net.SocksSocketImpl)
>  at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
>  at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
>  at java.net.Socket.connect(Socket.java:579)
>  at java.net.Socket.connect(Socket.java:528)
>  at java.net.Socket.(Socket.java:425)
>  at java.net.Socket.(Socket.java:208)
>  at clojure.tools.nrepl$connect.doInvoke(nrepl.clj:184)
>
> This thread then throws an exception which is logged to console:
>
> Exception in thread "Thread-4" java.net.ConnectException: Operation timed
> out
>  at java.net.PlainSocketImpl.socketConnect(Native Method)
>  at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.
> java:339)
>  at java.net.AbstractPlainSocketImpl.connectToAddress(
> AbstractPlainSocketImpl.java:200)
>  at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:
> 182)
>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
>  at java.net.Socket.connect(Socket.java:579)
>  at java.net.Socket.connect(Socket.java:528)
>  at java.net.Socket.(Socket.java:425)
>  at java.net.Socket.(Socket.java:208)
>  at clojure.tools.nrepl$connect.doInvoke(nrepl.clj:184)
>  at clojure.lang.RestFn.invoke(RestFn.java:421)
>  at clojure.tools.nrepl.ack$send_ack.invoke(ack.clj:47)
>  at clojure.tools.nrepl.server$start_server.doInvoke(server.clj:153)
>  at clojure.lang.RestFn.invoke(RestFn.java:619)
>  at user$eval2869.invoke(NO_SOURCE_FILE:0)
>  at clojure.lang.Compiler.eval(Compiler.java:6703)
>  at clojure.lang.Compiler.eval(Compiler.java:6693)
>  at clojure.lang.Compiler.eval(Compiler.java:6693)
>  at clojure.lang.Compiler.eval(Compiler.java:)
>  at clojure.core$eval.invoke(core.clj:2927)
>  at leiningen.core.eval$fn__6742.invoke(eval.clj:314)
>  at clojure.lang.MultiFn.invoke(MultiFn.java:231)
>  at leiningen.core.eval$eval_in_project.invoke(eval.clj:337)
>  at leiningen.repl$server$fn__10685.invoke(repl.clj:229)
>  at clojure.lang.AFn.applyToHelper(AFn.java:152)
>  at clojure.lang.AFn.applyTo(AFn.java:144)
>  at clojure.core$apply.invoke(core.clj:624)
>  at clojure.core$with_bindings_STAR_.doInvoke(core.clj:1862)
>  at clojure.lang.RestFn.invoke(RestFn.java:425)
>  at clojure.lang.AFn.applyToHelper(AFn.java:156)
>  at clojure.lang.RestFn.applyTo(RestFn.java:132)
>  at clojure.core$apply.invoke(core.clj:628)
>  at clojure.core$bound_fn_STAR_$fn__4140.doInvoke(core.clj:1884)
>  at clojure.lang.RestFn.invoke(RestFn.java:397)
>  at clojure.lang.AFn.run(AFn.java:22)
>  at java.lang.Thread.run(Thread.java:722)
>
> ... some time later ...
> REPL server launch timed out.
>
> Thanks, Neil
>
>  --
> 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 unsubscribe from this group and stop rece

Re: Thnx for clojureconj videos !!

[TP]

On Sat, Nov 22, 2014 at 5:09 AM, Geraldo Lopes de Souza <
geraldo...@gmail.com> wrote:

> Thank you very much for clojureconj videos !!


Not to be ungrateful, but it would be much better if all videos came with
"table of contents" that had links to the start times of each "Chapter",
"Section", "SubSection" (aka Slide) of the talk. YouTube supports this
automatically by converting text in the form of hh:mm:ss to links to that
point in the video. BTW this works even in comments so anyone can add TOCs,
but obviously it's better if the TOC is in the description.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

lein repl timeout

[Neil Laurance]

Hi there. Hope someone can help me with an issue I am having with lein 
repl. I did post on StackOverflow 
 
as well, but no luck there yet.

I have been using lein from my home Mac for quite some time, but hadn't 
started a repl for a couple of days.

When I came back to use lein repl again, it now fails with a timeout.

*Based on a hunch from another post, I managed to find a workaround of 
turning off my wifi which seems to resolve things ?!?*

But if anyone can help me with a better solution, that would be appreciated.

The lein version I am using is: Leiningen 2.5.0 on Java 1.7.0_11 Java 
HotSpot(TM) 64-Bit Server VM

I took a thread dump , 
which showed 'Thread-4' attempting to make a socket connection.

"Thread-4" prio=5 tid=0x7ffb6a0a nid=0x2707 runnable 
[0x000114aa8000] 
 java.lang.Thread.State: RUNNABLE 
 at java.net.PlainSocketImpl.socketConnect(Native Method) 
 at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) 
 - locked <0x0007f80aa8a8> (a java.net.SocksSocketImpl) 
 at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) 
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) 
 at java.net.Socket.connect(Socket.java:579) 
 at java.net.Socket.connect(Socket.java:528) 
 at java.net.Socket.(Socket.java:425) 
 at java.net.Socket.(Socket.java:208) 
 at clojure.tools.nrepl$connect.doInvoke(nrepl.clj:184)

This thread then throws an exception which is logged to console:

Exception in thread "Thread-4" java.net.ConnectException: Operation timed 
out
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:
339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(
AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:
182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
 at java.net.Socket.connect(Socket.java:579)
 at java.net.Socket.connect(Socket.java:528)
 at java.net.Socket.(Socket.java:425)
 at java.net.Socket.(Socket.java:208)
 at clojure.tools.nrepl$connect.doInvoke(nrepl.clj:184)
 at clojure.lang.RestFn.invoke(RestFn.java:421)
 at clojure.tools.nrepl.ack$send_ack.invoke(ack.clj:47)
 at clojure.tools.nrepl.server$start_server.doInvoke(server.clj:153)
 at clojure.lang.RestFn.invoke(RestFn.java:619)
 at user$eval2869.invoke(NO_SOURCE_FILE:0)
 at clojure.lang.Compiler.eval(Compiler.java:6703)
 at clojure.lang.Compiler.eval(Compiler.java:6693)
 at clojure.lang.Compiler.eval(Compiler.java:6693)
 at clojure.lang.Compiler.eval(Compiler.java:)
 at clojure.core$eval.invoke(core.clj:2927)
 at leiningen.core.eval$fn__6742.invoke(eval.clj:314)
 at clojure.lang.MultiFn.invoke(MultiFn.java:231)
 at leiningen.core.eval$eval_in_project.invoke(eval.clj:337)
 at leiningen.repl$server$fn__10685.invoke(repl.clj:229)
 at clojure.lang.AFn.applyToHelper(AFn.java:152)
 at clojure.lang.AFn.applyTo(AFn.java:144)
 at clojure.core$apply.invoke(core.clj:624)
 at clojure.core$with_bindings_STAR_.doInvoke(core.clj:1862)
 at clojure.lang.RestFn.invoke(RestFn.java:425)
 at clojure.lang.AFn.applyToHelper(AFn.java:156)
 at clojure.lang.RestFn.applyTo(RestFn.java:132)
 at clojure.core$apply.invoke(core.clj:628)
 at clojure.core$bound_fn_STAR_$fn__4140.doInvoke(core.clj:1884)
 at clojure.lang.RestFn.invoke(RestFn.java:397)
 at clojure.lang.AFn.run(AFn.java:22)
 at java.lang.Thread.run(Thread.java:722)

... some time later ...
REPL server launch timed out.
 
Thanks, Neil 

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Thnx for clojureconj videos !!

[juan.facorro]

+1

They are being uploaded withing a day or less from the actual recording 
which is extremely awesome!

https://www.youtube.com/playlist?list=PLZdCLR02grLoc322bYirANEso3mmzvCiI

On Saturday, November 22, 2014 10:09:04 AM UTC-3, Geraldo Lopes de Souza 
wrote:
>
> Thank you very much for clojureconj videos !!
>
>

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] freactive - high performance, pure Clojurescript, declarative DOM library

[Aaron]

Also, after discussions with several people at Clojure/conj, I see that it 
is necessary to provide some more documentation about how the bindings 
(components) and data structures in this library work differently from 
existing solutions (especially React) and what the overall vision is. Here 
are some rough draft docs I have:

The overall design idea for "renderer-agnostic" user interface conventions 
is here: https://github.com/aaronc/freactive.core/blob/master/UI-SPEC.md. 
Several people were excited about this idea and hopefully we can 
collaborate to make something along these lines happen. This document may 
also clarify how bindings (or lightweight components) are intended to work 
in this system and how they are different from (but also similar to) React 
components. 

I had originally intended to separate out the data structures (rx, atom, 
cursor) and put them in a separate library shared between projects. Here's 
a separate "freactive.core" project with some more details on the design 
goals behind my implementations of rx, atom and cursor plus a few 
implementation details (to be fleshed out more 
later): https://github.com/aaronc/freactive.core. There's also more details 
on these data structures 
here: 
https://github.com/aaronc/freactive#reactive-change-notifications-in-depth.

I'm still not totally happy with the name "freactive". Maybe something like 
"synergy" or "synergy-ui"?

Btw, it was nice to meet so many of you in person this weekend!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] freactive - high performance, pure Clojurescript, declarative DOM library

[Aaron]

> Regarding diffing - in terms of rerendering whole subtrees every time 
> reactive will not perform as well as react even if diffing is implemented - 
> it is not designed that way.
>

I should probably correct this - I think i was a bit tired when I wrote it 
and not as impressed with diffing performance as I wanted to be. Actually, 
although I've only done a very rough visual benchmark, I think the diffing 
performance is somewhat on par with React's - just no key support. Again, 
diffing isn't the core algorithm this library is using even though it has 
it - direct binding is.

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Safest way to isolate/terminate an uncooperative thread?

[Elliot]

If a thread becomes truly uncooperative (e.g. infinitely blocked or 
looping), is there any safe way to definitely kill it and recover its 
resources cleanly?  A consumer can deref with timeout, or take from channel 
with timeout, which protects the consumer.  But I'm not clear if that will 
do anything to clean up the state of the producer, which I presume will 
eventually degrade the system if threads or memory usage accumulate.

The concrete example in this case is that there are some types of weird 
HTTP failures/degradations that `clj-http` can't gracefully timeout/catch 
from, so it just hangs.  We're hoping to wrap this in some kind of process 
isolation that if _any_ type of error prevents returning a result within a 
timeout, the whole thing gets destroyed and cleaned up.

Any thoughts greatly appreciated.  Thank you!

- Elliot

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Amazonica: Clojure client for the entire AWS api

[Daniel Compton]

There is already a default release script included with recent versions of 
Leiningen. To do a release, simply run lein release :major, :minor, or :patch 
depending on the version bump that you want.

--
Daniel

> On 23/11/2014, at 1:06 pm, Sam Ritchie  wrote:
> 
> If you guys feel strongly, I'm sure the Amazonica maintainers would love a 
> pull req that adds a small release script that handles this for them. I'm 
> sure it'd get merged, and it'd be a nice, constructive way to move the 
> discussion forward.
> 
>> Gary Verhaegen  November 20, 2014 at 
>> 7:58 PM
>> On Thursday, 20 November 2014, Michael Cohen  wrote:
>> 
>> No idea about the rest, but for the github part I usually expect a tag for 
>> each release on Clojars, so if I want to read the actual code of the release 
>> I'm using it is easy to find it.
>> 
>> This should have a very minimal impact on your workflow: it should be 
>> limited to running git tag  once right after each release 
>> (or before; point is, if the unit of time is the git commit, it should be 
>> simultaneous).
>> 
>> Note that it is possible that you have created these tags and they are 
>> simply not on github because git does not push tags by default. You have to 
>> run git push --tags to push 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
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>> Michael Cohen   November 20, 2014 at 
>> 5:08 PM
>> 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 James Weaver's rotary library, and when you look at the
>> Javadocs, it almost seems like the Java SDK could be generated. So
>> that leads one to thinkand off I went.
>> 
>> As far as the problem areas you identified:
>> 
>> - shitty docs
>> What can I say, guilty as charged. Sorry. I tried to do a decent job
>> with the examples, although I laughed when I heard Stu Halloway slag
>> off "documentation by example" in some tech talk. Oops. What else
>> could I do? I looked at trying to generate some more codox type docs
>> from the Java SDK, but I just wasn't going to endure that pain. So,
>> yeah, I hear you. It's a trade off though. I'm sure there's a few
>> folks out there that would have to use Java interop and the Java SDK
>> (and pour through those same Javadocs) in order to use one of the less
>> popular AWS services if Amazonica didn't exist, because nothing else
>> would exist in the Clojure world for that particular AWS service. Man,
>> when I wrote this I don't even think there was a decent Clojure lib
>> for ec2.
>> 
>> - dynamically generated api
>> Yeah, the code is not as straightforward and reflection is expensive.
>> The counterpoint to that I guess would be, once you have it well
>> sorted, you don't really need to edit core.clj too much. And with most
>> of the AWS api, the cost of reflection is negligible compared to the
>> network hop. You're also probably not that concerned with latency at
>> all for those use cases. But again, it's a trade off. Buy one get 20
>> was worth a little reflection to me.
>> 
>> - Functions are both variadic and dispatch on argument type
>> Again, guilty as charged. I would do things differently today.
>> 
>> - 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 releases (less
>> frequently than Amazonica currently bumps the version numer)?
>> 
>> Mike
>> 
>> 
>> Greg Mitchell   November 20, 2014 at 
>> 1:32 PM
>> 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, and I've 
>> come to believe that some of the design choices in the library and its 
>> maintenance are big anti-patterns. All of these are things I've struggled 
>> with in developing against Amazonica:
>> 
>> * The d

Re: [ANN] Amazonica: Clojure client for the entire AWS api

[Sam Ritchie]

If you guys feel strongly, I'm sure the Amazonica maintainers would love 
a pull req that adds a small release script that handles this for them. 
I'm sure it'd get merged, and it'd be a nice, constructive way to move 
the discussion forward.



Gary Verhaegen 
November 20, 2014 at 7:58 PM
On Thursday, 20 November 2014, Michael Cohen > wrote:


No idea about the rest, but for the github part I usually expect a tag 
for each release on Clojars, so if I want to read the actual code of 
the release I'm using it is easy to find it.


This should have a very minimal impact on your workflow: it should be 
limited to running git tag  once right after each 
release (or before; point is, if the unit of time is the git commit, 
it should be simultaneous).


Note that it is possible that you have created these tags and they are 
simply not on github because git does not push tags by default. You 
have to run git push --tags to push 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
---
You received this message because you are subscribed to the Google 
Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to clojure+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.
Michael Cohen 
November 20, 2014 at 5:08 PM
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 James Weaver's rotary library, and when you look at the
Javadocs, it almost seems like the Java SDK could be generated. So
that leads one to thinkand off I went.

As far as the problem areas you identified:

- shitty docs
What can I say, guilty as charged. Sorry. I tried to do a decent job
with the examples, although I laughed when I heard Stu Halloway slag
off "documentation by example" in some tech talk. Oops. What else
could I do? I looked at trying to generate some more codox type docs
from the Java SDK, but I just wasn't going to endure that pain. So,
yeah, I hear you. It's a trade off though. I'm sure there's a few
folks out there that would have to use Java interop and the Java SDK
(and pour through those same Javadocs) in order to use one of the less
popular AWS services if Amazonica didn't exist, because nothing else
would exist in the Clojure world for that particular AWS service. Man,
when I wrote this I don't even think there was a decent Clojure lib
for ec2.

- dynamically generated api
Yeah, the code is not as straightforward and reflection is expensive.
The counterpoint to that I guess would be, once you have it well
sorted, you don't really need to edit core.clj too much. And with most
of the AWS api, the cost of reflection is negligible compared to the
network hop. You're also probably not that concerned with latency at
all for those use cases. But again, it's a trade off. Buy one get 20
was worth a little reflection to me.

- Functions are both variadic and dispatch on argument type
Again, guilty as charged. I would do things differently today.

- 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 releases (less
frequently than Amazonica currently bumps the version numer)?

Mike


Greg Mitchell 
November 20, 2014 at 1:32 PM
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, and I've come to believe that some of the design 
choices in the library and its maintenance are big anti-patterns. All 
of these are things I've struggled with in developing against Amazonica:


* The documentation is sparse and the code is not self-documenting.
Clojure in general tends to have worse and less documentation than 
Java. This is usually mitigated in well-designed Clojure libraries by 
being able to break into the source and read short, comprehensible 
functions with descriptive names. Amazonica is in the worst of both 
worlds by having no documentation in source, sparse documentation on 
github, and using dynamic

An introduction to writing and testing Clojure web apps

[Jarrod Taylor]

I published a five part blog series that walks through an introduction to 
writing and testing a Compojure application backed by a Postgres database. 

http://www.jarrodctaylor.com/posts/Compojure-Address-Book-Part-1/

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Lein :repl-options and using :init-ns functions does not evaluate namespace automatically

[Aleksandr]

I found that using (:gen-class) when defining namespace solves the issue, 
my functions become accessible.
But I don't really fully understand how it relates to lein repl in any way. 
I should probably try to run clojure in CLI, without lein, to better 
understand the process. It feels like lein masks a lot of behaviour, 
understanding which is quite important for efficiency.

On Saturday, November 22, 2014 1:10:01 PM UTC+1, Aleksandr wrote:
>
> I have defined in my project following repl configuration:
> :repl-options { :init-ns myproj.core }
>
> From my understanding, any repl session started should end up in 
> myproj.core
>
> Starting nrepl session (using cider-jack-in) in emacs does indeed show 
> myproj.core prompt
> myproj.core=> ...
>
> However, none of functions defined in the namespace are resolved. 
>
> myproj.core=> (server-start)
>
> CompilerException java.lang.RuntimeException: Unable to resolve symbol: 
> server-start in this context, 
> compiling:(/tmp/form-init4491116913200816459.clj:1:1)
>
> Once I do 
> (use 'myproj.core :reload)
>
> I can successfully use functions defined in NS:
>
> myproj.core=> (server-start)
> <... expected output>
>
> Why is my default namespace not evaluated when REPL session is started? 
> Couldn't find any answer in leiningen man or clojure namespace docs.
>
> Thanks for any insight!
>
>

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Lein :repl-options and using :init-ns functions does not evaluate namespace automatically

[Aleksandr]

I have defined in my project following repl configuration:
:repl-options { :init-ns myproj.core }

>From my understanding, any repl session started should end up in myproj.core

Starting nrepl session (using cider-jack-in) in emacs does indeed show 
myproj.core prompt
myproj.core=> ...

However, none of functions defined in the namespace are resolved. 

myproj.core=> (server-start)

CompilerException java.lang.RuntimeException: Unable to resolve symbol: 
server-start in this context, 
compiling:(/tmp/form-init4491116913200816459.clj:1:1)

Once I do 
(use 'myproj.core :reload)

I can successfully use functions defined in NS:

myproj.core=> (server-start)
<... expected output>

Why is my default namespace not evaluated when REPL session is started? 
Couldn't find any answer in leiningen man or clojure namespace docs.

Thanks for any insight!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] rete4frames, v. 5.2.1 - CLIPS-like expert system shell

[ru]

Hello all,

New version 5.2.1 of rete4frames CLIPS-like expert system shell published 
on https://github.com/rururu/rete4frames.

News:

1. Fixed nasty bug preventing matching of a variable slot in a pattern with 
an undefined slot in a fact.
2. Performance improvement by factor 2.
3. Corrected an example of an expert system for diagnoses some simple 
problems with a car, more conformity with the original CLIPS example.

Enjoy!

Sincerely,
  Ru

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Thnx for clojureconj videos !!

[Luc Préfontaine]

+1, could not make it to Washington, my agenda was tossed upside down last week 
but with
these at least I am not missing all of it.

Thank you,

Luc P.


> Thank you very much for clojureconj videos !!
> 
> -- 
> 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 unsubscribe from this group and stop receiving emails from it, send an 
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
--
Luc Préfontaine sent by ibisMail!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] rete4frames, v. 5.2.0 - CLIPS-like expert system shell

[ru]

Hello all,

New version 5.2.1 of rete4frames CLIPS-like expert system shell published 
on https://github.com/rururu/rete4frames.

News:

1. Fixed nasty bug preventing matching of a variable slot in a pattern with 
an undefined slot in a fact.
2. Performance improvement by factor 2.
3. Corrected an example of an expert system for diagnoses some simple 
problems with a car, more conformity with the original CLIPS example.

Enjoy!

Sincerely,
  Ru

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thnx for clojureconj videos !!

[Geraldo Lopes de Souza]

Thank you very much for clojureconj videos !!

-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.