Hi Everyone,
I've been out of the Clojure scene for about 18 months due to an
ill-advised detour into management. Don't worry! I've recovered pretty
well but I was wondering if anyone can suggest what I should be looking at
to bring me back up to speed.
My current context is that I have a me
I recommend starting with this excellent talk, if you haven't already seen
it: https://www.youtube.com/watch?v=qDNPQo9UmJA
Aside from that I recommend taking a look at Pedestal. It's async and
streaming capabilities are some of the most advanced you can find in the
Clojure space, and its protocols
Welcome back :-). Our latest application utilises EventSourcing,
domain events, DDD and CQRS and with Clojure's data-first and "it's
all just maps" it is a nice place to be. We are quite fortunate in
that all our consumers are Clojure(Script) so cljc, EDN and transmit
have made it even nicer.
The
3rd post in the series is now up thanks to Mike Fixes
https://clojurescript.org/news/2017-07-14-checked-array-access
On Mon, Jul 10, 2017 at 5:28 PM, David Nolen wrote:
> We have a series of blog posts in the queue that outline several major
> enhancements to the ClojureScript compiler that will
We use a wrapper around Dropwizard metrics which reports to Elasticsearch
and Kibana.
Nagios for alerting.
On Monday, July 10, 2017 at 4:35:33 AM UTC-4, Ćukasz Korecki wrote:
>
> Hi all!
>
> I'm wondering how people are getting application performance metrics out
> of their clojure applications
I have a few questions if this doesn't solve your issue, but how about
something as simple as:
(pmap (partial map handler) (partition-by splitter collection))
partition-by is lazy, and pmap is lazy-ish.
On Friday, June 16, 2017 at 10:13:11 AM UTC-4, Tom Connors wrote:
>
> I'm looking for a fun
This library is a work in progress, but is in a usable state and there is
unlikely to be any breaking changes to the api:
https://github.com/bcbradle/gl
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@goo
I see that it's uploaded to clojars so it might be a bit late to ask, but
what is the convention on naming libraries like this?
I'm used to seeing something like clj-gl for libraries that provide a
Clojure wrapper around an existing library.
Regardless, this is awesome and I hope to play with it
Are the docs out of sync? Because the README talks about immutable APIs and
seq to array conversions, but the library itself is just a renaming wrapper
mapping stuff like GL/GLVertex to gl-vertex. I don't understand how that
makes the API "modern". Unless that part isn't written yet.
Timothy
On F
This link:
https://dev.clojure.org/display/design/Improving+Clojure+Start+Time says
that the Java startup time is ~94 ms, while Clojure boot time is ~640 ms.
That's a ~680% increase.
On my machine the java start time is: ~1042 ms, and the Clojure start time
is around ~3108 ms. A ~298% increase
My mental model explains most of this away due to the different load
patterns of java vs v8. In JVM clojure, functions are essentially 1:1 with
classes, so in a functional language and standard lib, that's a lot of
classes. Java will eagerly classload your entire app and deps before doing
any wor
11 matches
Mail list logo