prospero

9 ms·

91.
Sleight: whole-program transformations for Clojure(github.com)
2 points by prospero 13y ago|0 comments
92.
Proteus: safe local mutable variables for Clojure(github.com)
2 points by prospero 13y ago|0 comments
93.
by prospero 13y ago
Uh, hey, I'm Zach. Thanks for the shout out. I'm mildly uncomfortable with you using Aleph as an example of good, idiomatic Clojure, but I suppose I can live with it. If you're looking through my code in the future and have
94.
by prospero 13y ago
I'm not one of the underrepresented groups, but I think it's irrefutable that these issues are central when introducing someone to a new technology and community. I understand that these issues are usually discussed separately f
95.
by prospero 13y ago
I think the point was that it's hard to make something failure-tolerant without being distributed. A locally persisted queue would avoid certain failure modes, though.
96.
by prospero 13y ago
Hey Allen, at Factual we're working on something in that vein: https://github.com/factual/skuld . As you might expect, doing it right takes something a bit more ambitious than just a library. If you're intere
97.
by prospero 13y ago
Nothing? Why all the fuss around hiring good developers, then?
98.
by prospero 13y ago
The linked report seems to suggest that the median time was 1.1 years, not 4.
99.
by prospero 13y ago
Wouldn't it be (O(n) + O(n) + ...) at the worst? And if it's on lazy sequences, which I thought it was, then composing a .Select and an .Aggregate should only involve a single pass through the sequence.
100.
by prospero 13y ago
http://docs.oracle.com/javase/6/docs/api/java/lang/Object.ht...
101.
by prospero 13y ago
Without knowing anything about hdf5 specifically, Vertigo [1] will let you treat a memory-mapped file (or a piece of one) as a normal Clojure data structure, as long as the element types are fixed-layout. [1] https://github.com&#
102.
by prospero 13y ago
It seems to me that there are real obstacles to that; since the propagation of messages from one channel to another requires a separate 'take' and 'put', there's some halting problem-style obstacles to figuring out
103.
by prospero 13y ago
CSP is message-oriented, Lamina is more stream-oriented. One implication of this is that in Lamina multiple threads can traverse the stream topology without any contention, but in core.async this isn't possible. Another is that the t
104.
by prospero 13y ago
Can you walk the chain of consumers and where they're forwarding the messages? I didn't see anything like that in the code, but you're far more familiar with it than I am.
105.
by prospero 13y ago
For those of you playing along at home, this is because of Clojure's reducers framework [1]. If we were to extend 'clojure.core.protocols.CollReduce' to ArrayList, we'd get similar performance, but the important point i
106.
by prospero 13y ago
The article mentions several independent failures to reproduce.
107.
by prospero 13y ago
The majority of of the article discusses the latest information about the NSA, and how we should hold NSA officials responsible for repeatedly lying to congress. Did you even bother to read it?
108.
by prospero 13y ago
There's the entire JVM ecosystem available. Batteries are very much included.
109.
by prospero 14y ago
You seem to have misread the above comment. Here's what it actually said: The system as a whole behaves more and more like a random router as the number of intelligent bamboo routing nodes increases The point is that this process was gra
110.
by prospero 14y ago
Some would also mention Aleph, too. https://github.com/ztellman/aleph
111.
by prospero 14y ago
That was what I was referencing, I was just on a phone at the time and didn't have the time or will to write it all out. I didn't know about the latter example, though, thanks for tracking that all down.
112.
by prospero 14y ago
You might look in The Clouds .
113.
by prospero 14y ago
Also a privateer and a mythical beast. I think there's sufficient prior art on this one.
114.
by prospero 14y ago
https://github.com/clojure/clojure/blob/master/src/jvm/cloju...
115.
by prospero 14y ago
Because keywords are functions which are implemented such that: (:keyword m) calls in turn (get m :keyword) That's just a basic feature of the language. No macros involved.
116.
The Secret History of Guns (2011)(theatlantic.com)
5 points by prospero 14y ago|0 comments
117.
by prospero 14y ago
Not my idea of what Apple is, and definitely not Steve's. Because Steve and me, see, we were like peas in a pod. He would have run this whole iPad Mini thing past me first.
118.
by prospero 14y ago
With respect to Lamina, that's just an example of a task on a separate thread being treated as an asynchronous result. It's entirely possible to use it to represent network communication or pretty much anything else.
119.
by prospero 14y ago
Nice false dichotomy you got there.
120.
by prospero 14y ago
I've talked to a lot of people about how they got into Clojure, and a fair number credit Paul Graham's essays for selling them on the idea of using a Lisp. I think there's a pretty clear causal link.

More ›