3 ms·
Interpreted languages often starts slow, yes. That is an issue with interpreted languages, not with CGI as a concept. If you trade low/no build time for high s
by vidarh 3y ago
Interpreted languages often starts slow, yes. That is an issue with interpreted languages, not with CGI as a concept.
If you trade low/no build time for high startup latency, by all means stay clear of CGI at all cost.
I've built fast CGI based systems, but not recently, because I prefer the convenience of an interpreted language, so I am not arguing you should prefer CGI.
Just that comparing a design pattern that is a consequence of not using CGI is a poor measure of CGI. If you were to seriously want to use CGIs, you wouldn't use runtimes that slow to start, or spread everything over hundreds of files, at least without a build step.