Hi all,
I'm very interested in taking part in CinC team, and going to submit an
application to this project at Google Summer of Code of this year.
Now I have some questions on CinC and where (and to whom) should I ask?
Is it ok to get in touch with Aaron directly?
Yuichi Nishiwaki
2013年4月16日
2013/4/21 Cedric Greevey
> That's very nice in theory; in practice, though, many contributors to and
> initiators of open source projects are hobbyist programmers that can't
> afford to spend $500/hr consulting a lawyer each time they want to decide
> on a license for a project.
I was referring
Hmm - I think I'm on to something.
I noticed that some of the nested maps were printing more than the first
element.
When i checked the _schema_ displayed by (protobuf-schema ) , all
the keys in the schema are lower case
The generated java classes for this proto are camelCase.
So the prin
Well, using the Lein protobuf generator at least helps with the Exception,
but it doesn't help with showing the full map. I didn't forget to import
the extensions.proto (which I thought would be the source of my problem
with the generated-for-java classes)
I haven't delved into the toString, bu
Can you open a ticket here with as much detail as possible?
https://github.com/aboekhoff/congomongo/issues
I don't know how many CongoMongo users are currently working with
shared collections.
Sean
On Fri, Apr 19, 2013 at 7:51 PM, Zhi Yang wrote:
> yes, it works for single instance, and for mo
Ah, great idea. Thanks!
-Steven
On Sat, Apr 20, 2013 at 5:25 PM, Michael Klishin <
michael.s.klis...@gmail.com> wrote:
>
> 2013/4/21 Steven Degutis
>
>> A friend posted about it on HN at
>> https://news.ycombinator.com/item?id=5582371 (there's no mailing lists
>> for Mac apps afaik)
>>
>
> St
On Apr 19, 2013, at 18:37, u1204 wrote:
> TL:DR
>
>Write ideas for humans around your code or it will die.
>Explain, don't document.
TL:DR "Computers should document.
Humans should explain."
More explicitly:
"Computers should document the things they can.
Well today has been the first chance I've had to try this, and
unfortunately, it's the same output. I _think_ the object ( and I use the
term loosely ) is being created more or less successfully, since I can
usually navigate to some of the sub-lists / maps
Not only that, but referencing one p
Hi everyone,
Releasing table 0.4.0, https://github.com/cldwalker/table#readme. table is
a smart ascii table renderer. It's similar to clojure.pprint/print-table
but more powerful.
Changes since the last release:
* Works with emacs nrepl
* Add :fields option to control field ordering
* Add :sor
PS. Of course the other key detail is that lazy sequences are realized
little by little (1 element at a time or up to 32, depending on
whether they're chunked or not; the original sequence here is chunked,
so the arrays underlying the chunks will be filled 32 elements at a
time, but then the iterat
On 20 April 2013 23:41, Tonino Jankov wrote:
> I mean, I think that in both cases the original sequence at one point in
> time must be, entirely realized, in memory.
Well no, it doesn't.
The original sequence is lazy and chunked, so it looks like a chain of
links holding 32 elements each. It so
On Sat, Apr 20, 2013 at 6:26 PM, Michael Klishin <
michael.s.klis...@gmail.com> wrote:
>
> 2013/4/21 Phil Hagelberg
>
>> It should go without saying, but don't take this as legal advice, etc;
>> please consult a legal professional before doing anything serious.
>>
>
> Definitely.
>
That's very n
2013/4/21 Phil Hagelberg
> It should go without saying, but don't take this as legal advice, etc;
> please consult a legal professional before doing anything serious.
>
Definitely.
I finally found the site I wanted to link to, TL;DR Legal:
http://www.tldrlegal.com/
Great overview of OSS licens
2013/4/21 Steven Degutis
> A friend posted about it on HN at
> https://news.ycombinator.com/item?id=5582371 (there's no mailing lists
> for Mac apps afaik)
>
Steven,
Sounds great! As for the mailing list, feel free to start a Google group
for your project. It's pretty easy to manage
and easy t
On Saturday, April 20, 2013 4:50:35 PM UTC-4, Phil Hagelberg wrote:
>
>
> I recommend the EPL; it's what you get when you
> run `lein new myproject`, and I feel like Rich made a pragmatic choice
> with a license that is copyleft without being virally so.
>
My understanding is that "copyleft"
I think what Michal is saying is that in "good" case, the original sequence
is cleared instantly upon being realized and in OOME case it hangs around,
so the issue is not the quantity of memory occupied by it, but also the
length of time interval it occupies the memory (in OOME case it stays in
mem
I mean, I think that *in both cases* the original sequence *at one point in
time* must be, entirely realized, in memory.
And if there is no doubling of it in critical case, what is critical?
If in (count t) (count d) - non.problematic- case original sequence also, *at
one poin*t, is, actually, in
Marko, you say "There is no doubling: *t* and *d* share the same underlying
lazy sequence and will refer to the same objects. The trouble is only that
you force the evaluation of *(count d)* while *(count t)* still waits to be
evaluated, so *t* must definitely stay bound to the head of the shared
s
Nice write-up. I took some of your advice in releasing Windows.app today:
- Put the source on github: https://github.com/sdegutis/windowsapp
- Made the readme concise and clear
- Added official docs right into the readme
- No longer making any breaking changes to API
- A friend posted about it on
Michael Klishin writes:
> It wasn't immediately clear to me, but it makes sense, given how short
> the MIT license is.
>
> What licenses does it make sense to recommend?
Given that Clojure libraries must be compatible with Clojure's license,
the GPL is ruled out. I recommend the EPL; it's what y
>> > but, in a nutshell, is literate programming:
>>
>> >
>> > 1. put possibly-out-of-order specially-marked (with an id) code snippets
>> >throughout your doc,
>> > 2. also put an *ordered* listing of all the id's somewhere in your doc,
>> > 3. use tools to find that ordered list of ids, then
2013/4/20 Phil Hagelberg
> Anyway, everything else about the post appears solid except for one
> thing. It recommends the MIT license, which has no patent protection
> whatsoever; this could open you and your users up to liabilities in ways
> that are impossible to predict given that the United S
On Sat, Apr 20, 2013 at 12:44 PM, u1204 wrote:
> >> The word "explain" is semantically the same as "document" to most
> >> people but not to the programmer community.
> >>
> >
> >FWIW, I think the situation is closer to precisely the opposite. If I ask
> >you to document what you do today, what w
On Saturday, April 20, 2013 3:35:04 PM UTC-4, da...@axiom-developer.org
wrote:
> > but, in a nutshell, is literate programming:
>
> >
> > 1. put possibly-out-of-order specially-marked (with an id) code snippets
> >throughout your doc,
> > 2. also put an *ordered* listing of all the id's somewhe
>> The word "explain" is semantically the same as "document" to most
>> people but not to the programmer community.
>>
>
>FWIW, I think the situation is closer to precisely the opposite. If I ask
>you to document what you do today, what will you do? Hold on to your
>receipts? Log mileage in your ca
On Saturday, April 20, 2013 11:52:29 AM UTC-4, Phil Hagelberg wrote:
>
>
>
> Anyway, everything else about the post appears solid except for one
> thing. It recommends the MIT license, which has no patent protection
> whatsoever; this could open you and your users up to liabilities in ways
> tha
>Hm. Maybe I should ask this off-list, but, in a nutshell, is literate
>programming:
I feel this is an "on-list" topic (although it is obvious that I'm an
edge-case fanatic). Clojure is trying to introduce a lot of new ideas
that change how programming is done. It is an edge-case community.
I'm
On Sat, Apr 20, 2013 at 11:51 AM, u1204 wrote:
>
> The word "explain" is semantically the same as "document" to most
> people but not to the programmer community.
>
FWIW, I think the situation is closer to precisely the opposite. If I ask
you to document what you do today, what will you do? Hold
>> TL:DR
>>
>> Write ideas for humans around your code or it will die.
>> Explain, don't document.
>>
>>
>Excellent post, Tim. Thanks for writing it all up.
>
>Though, I tend to think that "documenting" is the same as "explaining"
>(what good is documentation if it doesn't exp
On Sat, Apr 20, 2013 at 2:15 AM, Ken Scambler wrote:
>
> Lisp being Lisp, I rolled my own and it works fine. But I was wondering
> if there was an idiomatic way to do this in the standard library, without
> the repetition that cond necessitates when you are testing against a single
> value.
>
u
On Sat, Apr 20, 2013 at 12:47 PM, Cedric Greevey wrote:
> On Sat, Apr 20, 2013 at 5:15 AM, Ken Scambler wrote:
>
>> Hi there,
>> I'm getting started with Clojure, and found myself really missing
>> Scala-style pattern matching. Now I know about Matchure and core.match,
>> but all I really neede
On Sat, Apr 20, 2013 at 5:15 AM, Ken Scambler wrote:
> Hi there,
> I'm getting started with Clojure, and found myself really missing
> Scala-style pattern matching. Now I know about Matchure and core.match,
> but all I really needed was a cond using test predicates rather than
> boolean expressi
On Friday, April 19, 2013 9:37:52 PM UTC-4, da...@axiom-developer.org wrote:
>
> TL:DR
>
> Write ideas for humans around your code or it will die.
> Explain, don't document.
>
>
Excellent post, Tim. Thanks for writing it all up.
Though, I tend to think that "documenting" is
Hi there,
I'm getting started with Clojure, and found myself really missing
Scala-style pattern matching. Now I know about Matchure and core.match,
but all I really needed was a cond using test predicates rather than
boolean expressions, like this:
(condval value
foo-pred? (foo-result)
ba
Michael Klishin writes:
> My point was "at least try to find a new maintainer". Don't let it rot.
I see where you're coming from, but there's definitely a place for
phasing out a project gracefully. The majority of projects will have no
users outside the original author, and that's fine. There a
You've been bitten by laziness. Wrapping the concats in (doall ...) will
remove the stack overflows. The speed drop is probably from the concats
adding many additional list traversals. To fix both requires a
restructuring. You can change rst to a vector and use conj instead of
concat to append to i
Just tried again - using lein repl (clojure 1.4.0) and it worked fine.
It was late - who knows what I did ;-)
Thanks for checking guys.
On Saturday, 20 April 2013 02:37:14 UTC+2, Andy Fingerhut wrote:
>
> I fired up a Clojure 1.5.1 REPL, did (require '[clojure.string :as s])
> first, then copie
37 matches
Mail list logo
