I saw it and really like it. Particularly the part where the speaker
says that is impressed about what a small community with not much
funding can do. Because this is also truth and doesn't hurt at all.

I don't know about the garbage collector. In my case, the more I use the
image and load things on it, the more it becomes slow, but not really
that much and now I can bootstrap kind of the same state in other image
in a really reproducible way, including loading external interactive
Grafoscopio documents.

Talking about numbers, I think that Nadia Eghbal [1] and Benjaming Mako
Hill[2] are making a great job approaching critically to Libre Open
Source communities and demystifying the Bazar and Big Communities behind
peer production and showing how most of the projects are done by small
communities and how the average FLOSS project has a median of one
developer. That doesn't mean that we are living in a dreamed world,
because relying on one person for 97% of the FLOSS over there is clearly
and risk the more that infrastructure becomes digital and relying on
FLOSS. What that means is that we need to care about increasing the
single developer mean for the projects we are working on and that is a
concrete approachable goal. If the Pharo community can make some much
with so little, imagine what we can do with a median of three developers
for project! This is where promoting efforts should be located, in my
opinion.

[1] https://nadiaeghbal.com/
[2] https://mako.cc/

I shared the talk, and several of the Nadia's and Mako's links, with the
local Grafoscopio community (40 members in the Telegram chat and less
that 50 in the mailing list, with some members overlap between them and
with four average active members, not all coders).

Cheers,

Offray


On 23/11/18 18:29, horrido wrote:
> I didn't like the fact that he said the Pharo community was really, really
> tiny, even compared to the likes of Clojure.
>
> Because the truth hurts. 
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>


Reply via email to