Why does darwinports developers choose the tcl/tk for darwinports project?

[Daniel J. Luke]

On Dec 29, 2006, at 7:14 AM, Luc Heinrich wrote:
> In my very own and personal opinion, Tcl is the single reason why  
> MacPorts doesn't get as many external contributions as it should  
> and is therefore so awfully slow to evolve. I have tried to dive in  
> the MacPorts sources many times, read the Welch book, yadda yadda,  
> and I still can't get past 3 or 4 lines of Tcl without giving up in  
> disgust. Ok, maybe that's just me but still...

Maybe, but it was at least a sensible choice when the project was  
started and it's probably unreasonable to switch to something else  
given that we have over 3,702 ports (which are really just tcl  
programs).

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20061229/2ef41cdb/PGP.bin