You might want to add some commenting capabilities to those articles.
They'll be more valuable in the context of discussions IMO.
On 6 March 2015 at 18:49, Jozef Wagner wrote:
> Experiment #1
>
> *Deconstructing Core API*
>
> While Clojure provides its functionalities in multiple namespaces (e.g
Totally off the top of my head, but this should work -
(edn/read-string (join " " (line-seq r)))
Mark
On 7 March 2015 at 14:18, Sam Raker wrote:
> I'm experimenting a little with EDN files. I've currently got this
> function:
>
> (defn from-edn [edn-file] (with-open [r (clojure.java.io/reader
You're not using macros correctly.
A macro does not evaluate its arguments, but it does evaluate its return
value. The only thing a macro should do is to transform one piece of code
into another.
So let's look at what you want your syntax to look like:
(send! (function-blah "hi!"))
Now cons
>
> sorry for my crappy code, but I was changing some conditions and testing my
> parameters before and I end with this code
>
> (if (not (false? res))
res
(recur))
I must write just
(if res
res
(recur))
--
You received this message because you are subscribed to the Google
Hi guys, first I'm really noob using macros, basically I've this
( correct
address
res)))
I add this to gist https://gist.github.com/anonymous/9fc79679e17e36c47994
when I try run it I get: CompilerException java.lang.IllegalArgumentException:
Unable to resolve class
I'm experimenting a little with EDN files. I've currently got this function:
(defn from-edn [edn-file] (with-open [r (clojure.java.io/reader edn-file)]
(edn/read (java.io.PushbackReader. r
Having to explicitly reach into the Java API to read a clojure-only format
I'm trying to create an n-gram[1] corpus out of song lyrics. I'm breaking
individual songs into lines, which are then split into words, so you end up
with something like
{0 {0 "go" 1 "tell" 2 "aunt" 3 "rhodie"} 1 {0 "the" 1 "old" 2 "grey" 3
"goose" 4 "is" 5 "dead"}...}
(Yes, maps with integer
The whole "SSD fails after X number of writes" thing is pretty much a myth
now that most drives implement pretty aggressive write leveling. These
modern drives introduce a mapping layer between the physical disk locations
and the location written to by the OS. This means that writing to "KB 4242"
o
We have been running builds on the same SSDs, doing intensive logging, ... for
three years now.
None deteriorated.
Builds are mainly scrap & write thousands of small files plus a few big ones
(the targets).
Write speed makes a huge difference for this kind of task.
Aws allows to get VMs with
I'm under the impression that, because of the hard limit on writes, OSes
often already cache writes to SSDs, further limiting their usefulness in
this kind of application.
On Friday, March 6, 2015 at 4:10:54 PM UTC-5, Fluid Dynamics wrote:
>
> On Friday, March 6, 2015 at 3:16:09 PM UTC-5, Michae
Chestnut 0.7.0 has been deployed to Clojars.
Chestnut [1] is a leiningen template that provides a solid and complete
starting point for a web application using Clojure, Clojurescript, and Om.
It ships out of the box with a great development experience, including a
browser-connected REPL, insta
You can provide refs to dom calls and use om/get-node to retrieve them:
(dom/div #js {:ref "foo"} ...)
(om/get-node owner "foo")
It is tied to the owner though and I'm not entirely sure what that means
for grabbing refs from other components - as far as I'm aware, it will work
just fine for chil
On Friday, March 6, 2015 at 3:16:09 PM UTC-5, Michael Blume wrote:
>
> Possibly stupid question: can you just pretend you have more memory than
> you do and let the operating system do the heavy lifting?
>
As in, put the swap partition on the SSD and jack up the virtual memory in
the OS config?
Hello Alex,
On Wed, Mar 4, 2015 at 6:05 PM, Alex Miller wrote:
>
> To ensure the continued excellence and growth of the conference, we are
> excited that EuroClojure has joined the Cognitect ecosystem. Marco has been
> helping us and will continue to help make this conference awesome and
> impor
You could build something on top memory mapped files. I did this to solve
similar requirements with good effect.
On 6 Mar 2015 18:55, "JPatrick Davenport" wrote:
> Hello,
> I'm been thinking about an idea for a cache layer. It's driven by two
> trends.
>
> Most caches are in memory. They might ha
Possibly stupid question: can you just pretend you have more memory than
you do and let the operating system do the heavy lifting?
On Fri, Mar 6, 2015, 10:54 AM JPatrick Davenport wrote:
> Hello,
> I'm been thinking about an idea for a cache layer. It's driven by two
> trends.
>
> Most caches ar
Hello,
I'm been thinking about an idea for a cache layer. It's driven by two
trends.
Most caches are in memory. They might have fancy additions like
multi-machine, but they are in-memory. The fast memory access reduces back
end load and improves overall performance. It also assumes you have mem
Hmmm. You could use core.async, pass down a channel to children, and pass up an
event each time the child is mounted. The parent would start a go-loop on
initialization, count the children, and run some code when it gets the right
number of child-mounting events. You could also use a general eve
In ordinary React I think I would keep all of this logic in the parent, and
read from the DOM in didUpdate. There's a feature called refs which can be used
to grab references to the rendered children to get their DOM nodes.
I'm afraid I don't know how to do the equivalent in Om.
--
You receive
On 6 March 2015 at 17:48, Matthew Davidson wrote:
> Hmmm. You could use core.async, pass down a channel to children, and pass
> up an event each time the child is mounted. The parent would start a
> go-loop on initialization, count the children, and run some code when it
> gets the right number o
On 6 March 2015 at 15:29, Daniel Kersten wrote:
> I should have been clearer. I was thinking by using callbacks like Colin
> suggests. I've had code that looks like this before:
>
> (om/build component data {:opts {:cb #(om/set-state! owner %)}}
>
That's an interesting approach. I hadn't noticed
Experiment #1
*Deconstructing Core API*
While Clojure provides its functionalities in multiple namespaces (e.g.
clojure.string, clojure.zip), the majority of it is defined in a single
namespace called clojure.core. The first Dunaj experiment explores the idea
of having multiple small namespaces w
You need to use `ns-resolve' to resolve the actual vars you want to use.
Here's a snippet from one of our projects which shows the approach:
```clojure
(defn ws-repl []
(require 'cemerick.piggieback
'weasel.repl.websocket)
(let [cljs-repl (ns-resolve 'cemerick.piggieback 'cljs-repl
I'm using environ and lein-environ to pick up dev settings, such as
enabling weasel/piggieback in development.
In my server module, I'm running this code in -main:
(when (env :dev?)
(println "DEV")
(require 'pts.dev)
(pts.dev/browser-repl))
But pts.dev still throws a class not
I should have been clearer. I was thinking by using callbacks like Colin
suggests. I've had code that looks like this before:
(om/build component data {:opts {:cb #(om/set-state! owner %)}}
On Fri, 6 Mar 2015 14:43 James Reeves wrote:
> On 6 March 2015 at 09:13, Colin Yates wrote:
>
>> I know
On 6 March 2015 at 09:13, Colin Yates wrote:
> I know this is a different direction than a lot of people but I store
> everything in the app-state and so far it has worked well. There are a
> hundred reasons why this (storing everything in app-state) is a
> terrible idea, but I haven't run into a
On 6 March 2015 at 08:54, Daniel Kersten wrote:
> I've successfully used component local state for similar tasks while
> working with DimpleJS charts.
>
How so? I didn't think a parent component could access the local state of
its children.
- James
--
You received this message because you are
On 6 March 2015 at 05:22, Dave Della Costa wrote:
> (cc'ing clojurescr...@googlegroups.com)
>
> Let me make sure I understand what you're asking: you have a parent
> enclosing component that has to do calculations to position a set of
> child component element, but you can only properly calculate
Hi friends,
If you have any opinion about Immutant [1], would you please take a few
moments to fill out this short survey?
http://goo.gl/forms/syYnYtpM4v
We're trying to get a sense of how Immutant is being used.
Thanks so much!
Jim
[1] http://immutant.org
--
You received this message bec
I can confirm that there are a lot of companies training existing devs in
Clojure. I pretty regularly conduct training classes (for Cognitect) at
companies in this position, usually for 15-25 devs. Most commonly those devs
are coming from Java or Ruby. Some of those are well-known Clojure compan
Hey Dan & Michael,
I'd add this talk [1] to Neal's great talk as a cautionary tale before
trying to force things on nervous managers. Remember that a manager's #1
priority is keeping his own job, and being the guy who green-lighted an
experiment will get you fired (or at least sidelined) if the in
Regarding hiring, it seems to me that most of the smaller companies aren't
hiring clojure developers but rather training other developers.
I know one local former java shop that now mostly uses clojure for new
development and non of their team of ~10 had any prior clojure experience.
In my own sta
Haha this is the funniest thing I've read in a while! Good luck, forge on!
:)
On Thursday, March 5, 2015 at 7:47:41 AM UTC-8, Michael Richards wrote:
>
> I'm about to start training 4 devs on my team at Oracle in Clojure. My
> manager is very nervous about putting Clojure into the product. I'm
I'm planning to introduce experiments every other day, starting later today.
On Fri, Mar 6, 2015 at 12:05 AM, Alex Baranosky <
alexander.barano...@gmail.com> wrote:
> Yeah, I'm excited to see some of the 10 write-ups. What's the ETA on the
> first one?
>
> On Thu, Mar 5, 2015 at 6:02 PM, Alex Mil
I know this is a different direction than a lot of people but I store
everything in the app-state and so far it has worked well. There are a
hundred reasons why this (storing everything in app-state) is a
terrible idea, but I haven't run into any of them.
The main driver for this was for bug repor
I've successfully used component local state for similar tasks while
working with DimpleJS charts.
On Fri, 6 Mar 2015 05:46 Tom Lynch wrote:
> One workable possibility:
>
> * init a core.async channel in the container
> * pass the channel from the container into each child component at build
> t
36 matches
Mail list logo
