Hi rustaceans! What are you working on this week? Did you discover something new, you want to share?

  • GreenDot 💚@le.fduck.netEnglish
    0·
    7 months ago

    reverse proxy using tokio and hyper, there are few things to figure out on high traffic sotes, it doesn’t work as well compared to nginx after a certain threshold.

    • sugar_in_your_tea@sh.itjust.works
      0·
      7 months ago

      That’s too bad, I was thinking of replacing our nginx proxy with Rust. We need a little logic, so we currently have nginx -> gateway service -> microservice, and I was hoping to drop nginx. Maybe I still can, but it sounds like there would be some tradeoffs.

      • GreenDot 💚@le.fduck.netEnglish
        0·
        7 months ago

        Yeah, I’m looking at it, will probably rewrite the logic using Pingora. or maybe I did something wrong. Not sure if its something using the hyper legacy client, that has connection pooling, maybe there’s something there to improve.

        or maybe the use of RwLock to share the config struct is reaching some limits. Will try using parking_lot to see if anything changes.

  • Nereuxofficial@programming.dev
    0·
    7 months ago

    A general purpose memory allocator although this is really much a work in progress i think there are some good opportunities for otimization in a memory allocator for rust.

    For example Rust gives you the size of memory region to free, which means the allocator does not have to track that.

  • nebeker@programming.devEnglish
    0·
    7 months ago

    Just learning. I threw together a little CRUD API in Rocket the other day.

    Now I’m playing around with Diesel. I don’t love the intermediate New types, coming from EF Core. Is that because Rust ~~~~doesn’t really have constructors?

      • nebeker@programming.devEnglish
        0·
        6 months ago

        The insert on their Getting Started guide.

        let new_post = NewPost { title, body };

diesel::insert_into(posts::table)
    .values(&new_post)
    .returning(Post::as_returning())
    .get_result(conn)
    .expect("Error saving new post")

        Of course the other possibility is this guide is very low on abstractions.

        • sugar_in_your_tea@sh.itjust.works
          0·
          6 months ago

          Ah, I see. So you’re expecting to have one object for creation, updates, queries, etc.

          I work with something like that at work (SQLAlchemy in Python), and I honestly prefer the Diesel design. I build an object for exactly what I need, so I’ll have a handful of related types used for different purposes. In Python, we have a lot of “contains_eager” calls to ensure data isn’t lazy loaded, and it really clutters up the code. With Diesel, that’s not necessary because I just don’t include data that I don’t need for that operation. Then again, I’m not generally a fan of ORMs and prefer to write SQL, so that’s where I’m coming from.

          • nebeker@programming.devEnglish
            0·
            6 months ago

            One of my main concerns with this is the potential for making a lot of separate calls to the DB for a complex data structure. Then again there are trade offs to any architecture.

  • Cwilliams@beehaw.org
    0·
    7 months ago

    I just started writing a programming language! I’m using pest for the grammar/lexing, which makes if super easy. I built my ast using enums and structs, which makes me appreciate Rust even more. I also am coming to love the way rust handles errors. For example, when there’s an error converting from pest -> ast, it feeds all of the error into into my error type, which is so much easier to handle than making it panic out of the function