04:57 <Scramblejams> Is there any guidance on Pony library design? I see what seems like quite a bit of diversity in the reference capabilities of various classes and functions, and I often wonder why each was done that particular way.

04:58 <Scramblejams> Plus I'm planning to write my own library, and I have no idea how to structure its capabilities so it doesn't make its primary user (me) miserable. :-D

05:56 <jemc> Scramblejams: in general, the default capabilities should a good place to start, then change to different capabilities when the defaults are holding you back

05:58 <jemc> for example, when you create a `class Foo`, that translates to `class ref Foo` by default

05:59 <jemc> which is a good place to start until you have a reason to do otherwise

17:56 <Scramblejams> jemc: Thanks

21:08 <runehog> shouldn't this mention pony somewhere? :D https://en.wikipedia.org/wiki/Work_stealing

21:17 <SeanTAllen> it would make sense in the The idea of work stealing goes back to the implementation of the Multilisp programming language and work on parallel functional programming languages in the 1980s.[2] It is employed in the scheduler for the Cilk programming language,[3] the Java fork/join framework,[4] and the .NET Task Parallel Library.[5] area

21:32 <runehog> that's what I was thinking too. any suggestions for a paper to cite?