I worked at a company that acquired expage.com, which was a late 90s/early 00s homepage builder.
The entire site was a single C source file littered with embedded HTML, a few separate HTML files for things like an FAQ, and a directory of compressed user page data in some proprietary format (including images) that was decompressed on-the-fly. Served over Apache with some CGI magic.
While not a single C file, Fossil SCM also uses C with HTML inside it (it uses a custom preprocessor[0] for it), e.g. check the chat.c file[1]. The entire program ends up in a single binary file too.
> The entire site was a single C source file littered with embedded HTML, a few separate HTML files for things like an FAQ, and a directory of compressed user page data in some proprietary format (including images) that was decompressed on-the-fly. Served over Apache with some CGI magic.
I know that it is a very slender hope but it would be cool to see the source of this.
> [...] a directory of compressed user page data in some proprietary format (including images) that was decompressed on-the-fly. Served over Apache with some CGI magic.
This is pretty neat. I believe that was done to save on server storage, and before client side gunzip was a thing?
The entire site was a single C source file littered with embedded HTML, a few separate HTML files for things like an FAQ, and a directory of compressed user page data in some proprietary format (including images) that was decompressed on-the-fly. Served over Apache with some CGI magic.
https://web.archive.org/web/20000302105807/http://www.expage...