3 ms·
I got a 404 when trying to access the referenced blog post about CGI. https://web.archive.org/web/20210822121843if_/https://halestrom.net/darksleep/blog/046_cg
by 1vuio0pswjnm7 4y ago
I got a 404 when trying to access the referenced blog post about CGI.
https://web.archive.org/web/20210822121843if_/https://halestrom.net/darksleep/blog/046_cgi/ https://web.archive.org/web/20210822121843if_/https://halest...
https://webcache.googleusercontent.com/search?q=cache:https://halestrom.net/darksleep/blog/046_cgi/ https://webcache.googleusercontent.com/search?q=cache:https:...
"If I'm ever in the situation again of helping new people learn web technology then I'm going to get or convert them to use CGI right off the bat. It's easier to teach, it's easier to understand, easier to get working on most webservers and isn't locked in to any particular language or framework.
The only downside of CGI that I know about is the fact it starts a new process to handle each user request. Yes that's a problem in big sites handling hundreds or thousands of visitors per second. But by the time a new student gets to running a big site they will have already encountered many, many other scalability issues in their code and backend/storage. Let alone teaching them database and security concepts. There's a reason we have quotes like "premature optimisation is the root of all evil".
I don't think students new to webdev should be started on anything other than CGI. They can use any language they want. They can actually understand what they're doing. And they're not hitting any artificial barriers or limits set by frameworks or libraries."
OpenWRT still uses CGI
https://openwrt.org/docs/guide-user/luci/luci.on.lighttpd https://openwrt.org/docs/guide-user/luci/luci.on.lighttpd