Why You Should Not Use Tcl (1994)
groups.google.com
Why You Should Not Use Tcl (1994)
1–10 of 55 posts
Re: Why You Should Not Use Tcl (1994)
#2https://groups.google.com/g/comp.lang.tcl/c/7JXGt-Uxqag/m/vQ...
Re: Why You Should Not Use Tcl (1994)
#3See also Ousterhout's reply: https://groups.google.com/g/comp.lang.tcl/c/7JXGt-Uxqag/m/vQ...
> This is the proposition that you should use two languages for a large software system: one, such as C or C++, for manipulating the complex internal data structures where performance is key, and another, such as Tcl, for writing small-ish scripts that tie together the C pieces and are used for extensions.
Thankfully, today, we have great programming languages, like Python, that people enjoy using both for large software systems and for writing small-ish scripts.
So, I suppose Stallman was right? I definitely agree with him that Unix shell syntax is awful.
Re: Why You Should Not Use Tcl (1994)
#4See also Ousterhout's reply: https://groups.google.com/g/comp.lang.tcl/c/7JXGt-Uxqag/m/vQ...
Ousterhout's main argument seems to be: > This is the proposition that you should use two languages for a large software system: one, such as C or C++, for manipulating the complex internal data structures where performance is key, and another, such as Tcl, for writing small-ish scripts that tie together the C pieces and are used for extensions. Thankfully, today, we have great programming languages, like Python, tha…
Re: Why You Should Not Use Tcl (1994)
#5See also Ousterhout's reply: https://groups.google.com/g/comp.lang.tcl/c/7JXGt-Uxqag/m/vQ...
Ousterhout's main argument seems to be: > This is the proposition that you should use two languages for a large software system: one, such as C or C++, for manipulating the complex internal data structures where performance is key, and another, such as Tcl, for writing small-ish scripts that tie together the C pieces and are used for extensions. Thankfully, today, we have great programming languages, like Python, tha…
Re: Why You Should Not Use Tcl (1994)
#6See also Ousterhout's reply: https://groups.google.com/g/comp.lang.tcl/c/7JXGt-Uxqag/m/vQ...
Ousterhout's main argument seems to be: > This is the proposition that you should use two languages for a large software system: one, such as C or C++, for manipulating the complex internal data structures where performance is key, and another, such as Tcl, for writing small-ish scripts that tie together the C pieces and are used for extensions. Thankfully, today, we have great programming languages, like Python, tha…
Re: Why You Should Not Use Tcl (1994)
#7Other than that, it’s fine…
Re: Why You Should Not Use Tcl (1994)
#8A brief interview with Tcl creator John Ousterhout (2023) - https://news.ycombinator.com/item?id=41017367 - July 2024 (56 comments)
Previous discussions of current submission:
Why you should not use Tcl (1994) - https://news.ycombinator.com/item?id=14944103 - Aug 2017 (52 comments)
Why you should not use Tcl (1994, "The Tcl War") - https://news.ycombinator.com/item?id=7071479 - Jan 2014 (1 comment)
Re: Why You Should Not Use Tcl (1994)
#9Earlier quoted context omitted.
Ousterhout's main argument seems to be: > This is the proposition that you should use two languages for a large software system: one, such as C or C++, for manipulating the complex internal data structures where performance is key, and another, such as Tcl, for writing small-ish scripts that tie together the C pieces and are used for extensions. Thankfully, today, we have great programming languages, like Python, tha…
Stallman is always right, if you're willing to wait long enough.
Re: Why You Should Not Use Tcl (1994)
#10My thoughts.