Re: [tcljava-user] Reasons for using JACL?
Brought to you by:
mdejong
From: Scott S. <ss...@am...> - 2006-11-28 16:16:31
|
On 11/28/06 06:35, Kristoffer Lawson wrote: > On Mon, 27 Nov 2006, Scott Serr wrote: >> Kristoffer Lawson said: "Pure Java is quite simply inferior when it >> comes to writing tests or for dynamic stuff from the CLI or whatever. In >> fact, Java is inferior to Tcl for the core stuff as well, but I have no >> say in that matter." >> >> I'll take the otherside: "Tcl is simply inferior when it comes to core >> stuff, it's a mess. In fact, Tcl is inferior to Java (with BeanShell) >> for the scripting stuff as well, but I have no say in that matter." ;) > > You're probably the first person I know to claim that. Personally most > projects I have in Java would've been done much quicker in Tcl. > Protocols, > parameter mappings. Well, most stuff. Tcl is one of the cleanest > languages > out there (along with Lisp-variants), so I don't see how one can claim it > to be a mess? > > / http://www.fishpool.com/~setok/ Everybody has their preferences and I surely don't want to start a big thread on Tcl vs Java. But I will say this... Some people prefer dynamic languages - languages where you can redefine what "if" does. And where "#" comments behave like commands: proc a {} { # comment with unbalanced } } Dies. Some people like strongly typed languages. I know... "Strongly typed languages are for people with weak minds/memories." Also a compiler that *says* what line number it encountered an error on seems like a good thing. I guess what I'm saying is Tcl's grammar is clean and simple, but that doesn't necessarily translate to a good experience for the programmer. I have no doubt that you have mastered Tcl further than I have mastered any language. When you get to that point though you know what to avoid. -Scott |