Re: How Tcl speaks for itself and how Tcl is not spoken for...
- From: claird@xxxxxxxxx (Cameron Laird)
- Date: Fri, 22 Jun 2007 20:14:19 +0000
In article <1182529396.126408.290450@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Patrick Finnegan <finnegan.patrick@xxxxxxxxx> wrote:
.
.
.
Tcl is a great language but it has no traction in the corporate
world. Java programmers will move to Groovy rather than Python or
Ruby. I see people starting out with Groovey and progressing to
Java for more complex performant applications.
Heck, I see organizations take working applications coded in
Tcl, and rewrite them in Java to gain performance. In fact
they *lose* performance and functionality, and the rewrite
takes more time than the original development, but those
weren't the intentions, so ...
.
- Follow-Ups:
- Re: How Tcl speaks for itself and how Tcl is not spoken for...
- From: skuhagen
- Re: How Tcl speaks for itself and how Tcl is not spoken for...
- From: Patrick Finnegan
- Re: How Tcl speaks for itself and how Tcl is not spoken for...
- References:
- How Tcl speaks for itself and how Tcl is not spoken for...
- From: skuhagen
- Re: How Tcl speaks for itself and how Tcl is not spoken for...
- From: Patrick Finnegan
- Re: How Tcl speaks for itself and how Tcl is not spoken for...
- From: Damon Courtney
- Re: How Tcl speaks for itself and how Tcl is not spoken for...
- From: Patrick Finnegan
- How Tcl speaks for itself and how Tcl is not spoken for...
- Prev by Date: Re: 0.7.8 ttk::treeview missing -xscrollcommand option?
- Next by Date: Re: bash scp statement not working correctly
- Previous by thread: Re: How Tcl speaks for itself and how Tcl is not spoken for...
- Next by thread: Re: How Tcl speaks for itself and how Tcl is not spoken for...
- Index(es):
Relevant Pages
|