• wolo@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 months ago

    my website’s backend is made with bash, it calls make for every request and it probably has hundreds of remote arbitrary code execution bugs that will get me pwned someday, it’s great

    edit: to clarify, it uses a rust program i made to expose the bash scripts as http endpoints, i’m not crazy enough to implement http in bash

    it behaves like a static file server, but if a file has the others-execute permission bit set it executes the file instead of reading it

    it’s surprisingly nice for prototyping since you can just write a cli program and it’s automatically available over http too

  • agilob@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 months ago

    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
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      8 months ago

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

      • voxel@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        8 months ago

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

        • sebsch@discuss.tchncs.de
          link
          fedilink
          arrow-up
          1
          ·
          8 months 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
      link
      fedilink
      arrow-up
      1
      ·
      8 months 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.