If Scheme is so good why MIT drops it?

Tayssir John Gabbour tayssir.john at googlemail.com
Sat Jul 25 03:23:45 EDT 2009


On Jul 24, 11:58 pm, ACL <anonymous.c.lis... at gmail.com> wrote:
> I actually think that the thing holding lisp back is 'bus factor'.
>
> Lets assume I have a java project and a lisp project:
>
> Java project:
> I have maybe 10 or 12 people on my team working on various subsystems
> of my project. There are probably one or two 'technical leader' types
> in the group, and a bunch of others who are sort of 'serfs', banging
> out java classes. Lets say one of my important guys gets totally
> splattered by a bus... I've still got another one left! I can rely on
> the other guy to keep things afloat while I train up a new leader
> type.
>
> Lisp project:
> I don't need as many people. I have 3 or 4 people, and one person is
> my technical leader and lisp guru. Guru is probably in charge of more
> difficult macros and (because of that), also in charge of the overall
> design (macros are design patterns embodied in code). Lets say he gets
> totally annihilated by the bus. What do I do now? I had all my eggs in
> one basket and my project is now stalled.

A Clojure programmer mentioned interesting solutions to this used by
his company, such as partnerships with similarly Agile companies.
http://programmingtour.blogspot.com/2009/07/conversation-with-stuart-halloway.html

I agree that the bus factor -- as well as some other problems -- works
against Lisp's acceptance.


All the best,
Tayssir



More information about the Python-list mailing list