One of those learnings, was that I never wanted to again use a dynamic language without any kind of JIT compiler for full blown web servers.
The language is great, rewriting Tcl libraries into C on regular basis due to performance issues not so much.
What about a dynamic language with an AOT compiler? E.g. SBCL implements Common Lisp by compiling everything ahead of time.
However in regards to dynamic languages, unless they support and make use of type annotations with an optimizer compiler, JIT will always perform better than AOT, due to what is possible to do in those languages.
That is why AOT toolchains in Java and .NET world are actually JITs in disguise, because while the languages look static, they inherited much of Smalltalk and Objective-C dynamism that inspired Java semantics, only the syntax was done in a way to be attractive to C++ folks.
And you're not kidding about everything being a command - this here is some "what the fuck is wrong with you people": https://wiki.tcl-lang.org/page/comment
Including the truly stunning collection of:
- one must terminate the command with ; before one can comment
- one cannot have mismatched braces so don't try to comment out bogus code
- one cannot have a backslash in a comment but hey it's a feature not a bug because this is how they launch wish:
#!/bin/sh
# the next line restarts using wish \
exec wish8.0 "$0" "$@"
since the backslash is ignored by the shell but parsed by wishhttps://github.com/TPC-Council/HammerDB/blob/master/src/post...
tcl makes as an alright shell script language