[Seaside] social coding for smalltalk (was Re: [squeak-dev] Re:
[Pharo-project] SqueakSource AND SmalltalkHub down)
sebastian at flowingconcept.com
Wed Apr 20 13:36:25 UTC 2011
"Ahother github" is nutty. I don't see any signal of market space for that. At least not without some radical innovation that the market is probably unprepared to swallow at this point.
So we play the game there or we simply don't change.
On Apr 20, 2011, at 10:27 AM, Davorin Rusevljan wrote:
> On Wed, Apr 20, 2011 at 3:13 PM, Sebastian Sastre
> <sebastian at flowingconcept.com> wrote:
>> Sort of... clarifying:
>> 1. not being at all where people is, is actually an issue (from the social POV is a primary issue, from the technical POV is a secondary issue) and
>> 2. commenting at method level is an issue (because we are inefficient in "using society" to help code in projects get better (also to convert newcomers easier)).
>> If the code isn't exposed (visible in the UI) then we are not socializing code.
>> Which leads to this question:
>> If we aren't socializing code in a world that is
>> 1. getting more social (at near-light-speed) and
>> 2. more connected (faster than light)...
>> then how you can say (and keep your face straight) that you are "inventing the future"?
>> You are not. Not one the world is clearly demanding (so you'll not have an expanding market, you'll have a shrinking market)
>> It's only me that see things like this here?
> err.. some big (buzz)words for me, but:
> 1) agree that non presence on github is big issue
> 2) building something like github, but for smalltalk only could be:
> a) huge task
> b) maintenance hog
> c) may result in functionality less stellar than expected because
> of a + b, and as result worsening 1
> Davorin Rusevljan
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside