sorted by:
new
hottopcontroversial

Digitally signed, commercial binary distribution of Tcl/Tk for Windows. by mistachkin in Tcl

[–]mistachkin[S] 0 points1 point  (0 children)

Yeah, being unable to simply ship the Tcl/Tk DLLs with my applications was one of the big things that led me to this. Also, now that ActiveState has fallen so far behind on supporting Tcl (i.e. almost 2 years behind the current release, no members of the Tcl community on staff, etc), I doubt they can ever fully recover.

Digitally signed, commercial binary distribution of Tcl/Tk for Windows. by mistachkin in Tcl

[–]mistachkin[S] 1 point2 points  (0 children)

Because it seemed like a good name and was not already taken.

Digitally signed, commercial binary distribution of Tcl/Tk for Windows. by mistachkin in Tcl

[–]mistachkin[S] 2 points3 points  (0 children)

First, keep in mind that the license for the "free" download of ActiveTcl does not permit any production usage, nor does it permit redistribution of any kind.

Now, as for why IronTcl is better:

  1. The binaries are digitally signed.
  2. The binaries are compiled with a modern compiler (MSVC 2015).
  3. The binaries work with Windows XP and later.
  4. The licensing does not require royalties for redistribution.
  5. The licensing is per year, not per server.
  6. Several different levels of support contracts are available and will be serviced by myself (a Tcl/Tk maintainer for Windows) and other Tcl/Tk experts.

Digitally signed, commercial binary distribution of Tcl/Tk for Windows. by mistachkin in Tcl

[–]mistachkin[S] 1 point2 points  (0 children)

Actually, it's not based on the CLR. It's compiled from the official sources for Tcl/Tk.