Re: [Esug-list] Few thoughts about Google Summer of Code

M
mkobetic@cincom.com
Fri, Oct 29, 2010 3:58 PM

"Paolo Bonzini"bonzini@gnu.org wrote:

Ability to work seamlessly with people that use the tools outside
Smalltalk is already a big step forward.  It will often do even if the
integration with the tool is kind of fake.

Sure, but that just helps you to do part of a project in smalltalk, it doesn't help much with attracting new people to Smalltalk.

"Paolo Bonzini"<bonzini@gnu.org> wrote: > Ability to work seamlessly with people that use the tools outside > Smalltalk is already a big step forward. It will often do even if the > integration with the tool is kind of fake. Sure, but that just helps you to do part of a project in smalltalk, it doesn't help much with attracting new people to Smalltalk.
PB
Paolo Bonzini
Fri, Oct 29, 2010 4:10 PM

On 10/29/2010 05:58 PM, mkobetic@cincom.com wrote:

"Paolo Bonzini"bonzini@gnu.org  wrote:

Ability to work seamlessly with people that use the tools outside
Smalltalk is already a big step forward.  It will often do even if the
integration with the tool is kind of fake.

Sure, but that just helps you to do part of a project in smalltalk,
it  doesn't help much with attracting new people to Smalltalk.

It's definitely a step towards that, though.  Does your experience with
CVST suggest that it's better to do both steps at the same time?

I would be worried that including in an "initial battle plan" an
editor-friendly syntax would lead to endless discussions and no code
produced.

Paolo

On 10/29/2010 05:58 PM, mkobetic@cincom.com wrote: > "Paolo Bonzini"<bonzini@gnu.org> wrote: >> Ability to work seamlessly with people that use the tools outside >> Smalltalk is already a big step forward. It will often do even if the >> integration with the tool is kind of fake. > > Sure, but that just helps you to do part of a project in smalltalk, > it doesn't help much with attracting new people to Smalltalk. It's definitely a step towards that, though. Does your experience with CVST suggest that it's better to do both steps at the same time? I would be worried that including in an "initial battle plan" an editor-friendly syntax would lead to endless discussions and no code produced. Paolo