1. 40

  2. 6

    I was a bit disappointed that there wasn’t a final evolution punchline waiting at the bottom in the form of an obvious and elegant solution.

    1. 3

      It was an elegant solution to the job security program. Good luck hiring another person who (a) knows Rust and (b) can maintain that pile of code.

      1. 1

        Could you expand? How is Rust viewed in the security community, both as a target for attacks and as a language to possibly write safer programs?

        1. 3

          It was a joke about how some people build overly-complex code on purpose to make the worker a necessity the company can’t get rid of. The Rust code toward the end could be examples.

          Far as security community, I cant say given Im not in mainstream, security community. I know a few here like that it prevents more code injections by default. I know security and non-security folks like the no-GC safety if they can stand the borrow-checker. Far as high-assurance systems, I’m against it other than for prototyping because C and Ada/SPARK have more tools to find/prevent errors with a certifying compiler for C. Plus, safety-critical folks might use them.

          Now, there’s another group among C developers that believe stopping errors is the programmer’s responsibility, that C is adequate for such people to write error-free code, optionally that its syntax/semantics are better than others, and compiler-to-binary isnt an issue (except Karger/Thompson Attack). Some people in this crowd will use some tooling, esp sanitizers. You can’t get them to switch to a safer language or use high-assurance methods due to their ideological beliefs about programming.

          So, I try to figure out which Im talking to fast so I dont waste our time on stuff they’ll ignore. I try to give each group what might help them, though, among methods they might want to use.

      2. 3

        The good answer were hidden in the middle. “Junior Rust Programmer” and “Functional Rust Programmer”. The error pattern in “Senior Rust Programmer” is a good read too, but obviously tad complected for such a small thing.

        1. 2

          I think the first one was supposed to be the right one. I don’t really read Rust, but the first one was the only one I could mostly understand.

        2. 2

          My version of proc_macro:

          fn main() {}

          (library implementation up to the reader)

          1. 1

            Dang, the effort is amazing.

            joined the “It should be removed in favor of expect() “-movement

            haha that was me sometimes