Awesome!, Thanks a lot Mike.
On Tue, Jul 21, 2015 at 4:30 AM, Andrew Keedle wrote:
> Brilliant Mike. Well done with this. Very impressive.
>
> On Monday, 20 July 2015 21:28:51 UTC, Mike Fikes wrote:
> > Replete 1.0 is now in the App Store
> >
> >
> http://blog.fikesfarm.com/posts/2015-07-20-ios
Don't bother please, after I upgraded the clojure-mode issue got fixed.
Again thanks for your magnificent tool.
Best regards
Shahrdad
On Tue, Jun 16, 2015 at 12:19 PM, Shahrdad Shadab
wrote:
> Hi Bozhidar
>
> Thanks for the awesome work however when I upgraded to version 0
Hi Bozhidar
Thanks for the awesome work however when I upgraded to version 0.9 I get
the following error when starting cider in emacs:
Starting nREPL server via lein repl :headless...
nREPL server started on 55266
nREPL: Establishing direct connection to localhost:55266 ...
nREPL: Direct connecti
Hi Morteza
I have been doing Clojure past two years. Please find my Resume attached.
Best Regards
Shahrdad
On Thu, Jun 4, 2015 at 3:45 AM, Murtaza Husain <
murtaza.hus...@sevenolives.com> wrote:
> Hi,
>
> A friend's startup is looking for couple of clojure devs. Its a startup
> and the stack t
erenced "data" does not.
>
> - James
>
> On 5 April 2015 at 18:00, Shahrdad Shadab wrote:
>
>> Hi folks
>>
>> It may seem silly question but why when I doseq over a vector that is
>> wrapped in an atom and change the vector using swap! while I am
Hi folks
It may seem silly question but why when I doseq over a vector that is
wrapped in an atom and change the vector using swap! while I am inside
doseq, the doseq sets to the beginning of the vector intermittently:
(def a-data (atom [15 9 8 1 4 11 7 12 13 14 5 3 16 2 10 6]))
(defn switch-tw
This is another way of saying "Do not point the contrast between Clojure
and other technologies just because I don't know those technologies".
I believe showing the clear contrasts (and in general pain points in this
field) by people like me who worked in both Clojure and non clojure
technologies f
Trust me I have been using Scala + Akka + Play for past three years in
production, and had to deal with tons of incidental complexity plus a lot
of noise they introduce as my daily job (in my code as well as other
developer's code). Now I am in the best position to judge and compare them
with Cloju
Awesome!
It was about the time that someone shows the power of clojure in reactive
programming (and in particular core async) to the practitioners that use
Scala / AKKA for orchestration.
I personally work in a company that some ignorant architect decided to
Java8 + Akka + play's promise facilit
Great Job Bozhidar! Thanks for the quality software.
On Mon, Dec 22, 2014 at 8:38 AM, Sun Ning wrote:
> Good Job, Bozhidar! I've already updated from MELPA. Everything works like
> a charm.
>
>
>
>
>
> On 12/21/2014 08:39 PM, Bruce Durling wrote:
>
>> Thanks!
>>
>> cheers,
>> Bruce
>>
>> On Sun,
My Apologies to the group. Please disregard my last email.
Thanks a lot
Best Regards
Shahrdad
On Mon, Nov 17, 2014 at 11:17 AM, shahrdad shadab <
clojure.langu...@gmail.com> wrote:
> Hi Eric
>
> I have been doing Clojure for about a year ,please find my Resume.
>
> Thanks
p 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.c
ate a number of elements in advance. Often the outputs
>> from the various list handling functions are chunked (e.g. map, range,
>> etc.), while creating a seq explicitly with lazy-seq will not be chunked.
>>
>> - James
>>
>> On 18 October 2014 18:28, shahrdad shad
Greeting everyone,
It might be stupid question but I expect
(first (map (fn [_] (println "executed")) [1 2 3 4]))
prints only once (realizing only first element in lazy seq returned by map)
but it prints four times.
Can some one shed a light why?
Thanks in advance
Best regards
Shahrdda
--
Hi folks
I know when I send/send-off an action to an agent within a STM transaction
no action will be
dispatched if transaction fails to commit.
I was expecting similar behaviour when agent fails: the transaction does
not commit when
the action puts the agent in an invalid / failed state.
It seem
Yet another way:
(reduce #(let [[k [v1 v2]] %2] (vec (concat % [[k v1]] [[k v2]]))) [] [[:a [1
2]] [:b [3 4]]])
On Jun 8, 2014, at 3:43 PM, boz wrote:
> Thanks for the replies!!
>
> I goofed and only gave part of my loopy solution ...
> here's the whole thing
>
> (defn do-one [id v]
16 matches
Mail list logo