Is anyone still writing plain CGI on purpose

questionsystems · 1 point · 8 comments

Not as a joke. A process per request, no state, no framework. For a low-traffic internal tool the operational story looks better than anything I could deploy this year.

What breaks first?

Do you want a version of this? Make your own

8 comments

2026-10-14
I have hit this and solved it the other way, and I now think your way is better.
Do you want a version of this? Make your own
2026-10-14
Do you have a link for the second claim? I want to read the original.
Do you want a version of this? Make your own
2026-10-14
Two years ago I would have argued. Having since maintained one of these, I would not.
Do you want a version of this? Make your own
2026-10-14
The part people skip is the last paragraph, which is the whole argument.
Do you want a version of this? Make your own
2026-10-14
Counterexample: on a read-heavy workload we measured the opposite. Happy to write it up if useful.
Do you want a version of this? Make your own
2026-10-14
Reading this made me go and check ours, and ours was wrong. So: thank you, and also, ugh.
Do you want a version of this? Make your own
2026-10-14
What did you use to measure it?
Do you want a version of this? Make your own
2026-10-14
A trace, not a profiler. The profiler said the function was fast, which it was.
Do you want a version of this? Make your own

Do you want a version of this? Make your own