The pest book is finally complete now! 🎆 (sort of) · pest-parser pest · Discussion #1105
github.com
For ages, the pest book would end with the unfinished "Final project: Awk clone (WIP)" chapter. The plan for this chapter was proposed by @wirelyre a long time ago: pest-parser/book#5 (comment) One...

https://pest.rs/book/examples/awk.html 🎉

I aimed to keep it in line with the “demonstration of the Rust ecosystem” goal, so it can also be a great introduction to Rust for beginners who are looking for a fun project to work on. It’s not perfect, but that’s part of the fun! It leaves room for potential language extensions (to make the AWK clone more complete) and optimizations up to the reader as a follow-up.

  • TehPers@beehaw.orgEnglish
    0·
    5 months ago

    I’m not sure why this surprises you. MIT OR Apache is standard for Rust libraries.

    Not everyone wants to copyleft their code. People write these libraries with different goals in mind, and sometimes someone wants to use their own library in their own closed source project.

    • Hugh@slrpnk.net
      0·
      5 months ago

      Then they can release it publicly under the GPL and then privately license it to their employer under hopefully specific terms, ideally for a fee. There’s no good reason to let for-profit companies reap the value out of FOSS.

      • TehPers@beehaw.orgEnglish
        0·
        5 months ago

        Public contribitions would be licensed under GPL and owned by the contributor. They would not be allowed to use those contributions themselves without releasing their product as open source.

        • moonpiedumplings@programming.dev
          0·
          5 months ago

          You can do what’s called dual licensing, where you make contributes sign an agreement where they give up their code to the org so the org could take it proprietary.

          Part of the controversy over Ubuntu’s changes to LXD was the change to this dual licensing setup from a permissive license.