Before nginx was a thing, I worked with a guy who forked apache httpd and wrote this blog in C, like, literally embedded html and css inside the server, so when he made a tpyo or was adding another post he had to recompile the source code. The performance was out of this world.

[–] Schmeckinger@feddit.de 2 points 2 years ago* (last edited 2 years ago) (1 children)

There are a lot of solutions like that in rust. You basically compile the template into your code.

[–] vox@sopuli.xyz 1 points 2 years ago* (last edited 2 years ago) (1 children)

yeah, templates can be parsed at compile time but these frameworks are not embeeding whole fucking prerendered static pages/assets

[–] sebsch@discuss.tchncs.de 1 points 2 years ago

They are nowadays. Compiling assets and static data into rust and deliver virtual DOM via websocket to the browser is the new cool kid in the corner.

Have a look at dioxus

[–] bazsalanszky@lemmy.toldi.eu 1 points 2 years ago

This reminds me of one of my older projects. I wanted to learn more about network communications, so I started working on a simple P2P chat app. It wasn't anything fancy, but I really enjoyed working on it. One challenge I faced was that, at the time, I didn't know how to listen for user input while handling network communication simultaneously. So, after I had managed to get multiple TCP sockets working on one thread, I thought, why not open another socket for HTTP communication? That way, I could incorporate a fancy web UI instead of just a CLI interface.

So, I wrote a simple HTTP server, which, in hindsight, might not have been necessary.