[pjmlp]

On first startup we used Tcl, and C code for performance, similar to what is fashionable with Python nowadays.

I had enough of the rewrite in C experience that since then, if the language doesn't come with a compiler on the box, either JIT or AOT, I only see it as scripting language for sysadmin work or learning purposes.

[mmcgaha]

AOLServer had a lot of defaults that would magnify the performance issues of TCL. The documentation did not cover all of the necessary configuration options to get a system to scale and you had to dig into driver.c to understand how to tune the system. I think the two big undocumented bottlenecks were maxsok and backlog. I bet if you were writing the same applications today, using modern hardware and Naviserver you would not have to write C modules anymore.

[pjmlp]

Our product was a competitor to AOLServer with CMS tooling for call centers.

Also Vignette, remember it?

When we dediced to move away from TCL/C, after exhausting the performance options, J2EE was going to be the next version.

Due to a twist of fate of being Microsoft partners, we got invited to take part into .NET launch product line, and that Java rewrite became a .NET one instead.

The original founders, after going through these experiences, went out and created OutSystems based on the learnings, naturally in .NET and later a Java backend was added as well.