1. 75
  1.  

  2. 14

    Zig is such a promising language.

    I hope it becomes great for deploying applications as well, and plays nicely with various package managers and Linux distros.

    Deployment seems to be an afterthought for some programming language ecosystems.

    1. 24

      Deployment seems to be an afterthought for some programming language ecosystems.

      If you check the 4th commit in ziglang/zig repository, the commit that first populated the README.md file with a set of goals for the project, this goal is listed:

      • Friendly toward package maintainers.

      I’ve been a Debian and Ubuntu package maintainer in the past, and I even picked up another Debian Developer from the airport in order to sign each other’s gpg keys (part of the procedures to gaining upload access).

      I’ve also been involved in the Node.js ecosystem - looks like I have 76 packages under my name.

      I’m familiar with what distribution maintainers want to achieve for their users, and the problems they are faced with in terms of packaging, as well as what upstream project maintainers want to achieve for their users, and I’m intimately familiar with how these goals can sometimes conflict. I fully intend to use this insight to help both parties work more effectively with each other for the end user when it comes to the Zig package manager, ecosystem, and communities.

      1. 2

        That sounds perfect! Thanks for creating Zig, I really like the philosophy behind it.

        Now all I’m longing for is Zig++, a language just like Zig, but with added syntactic sugar. ;)

    2. 5

      Ah man, I’m a bit disappointed there wasn’t much discussion of the new data model. I would have been very interested in seeing what made the new version more efficient and why zig is a better language for implementing it than C :\

      1. 7

        As mentioned in the article, it seems that Zig was not chosen because it allowed more things, but because it was easier and more fun to prototype on it… and it ended up with a full V2.

        1. 3

          Ask for a follow-up!!

          1. 12

            Asked the author and he told me on the fediverse that he do plan to do a followup adressing the data model comparisons and how doing it in C would have been more painful.

          2. 2

            The Zig source is very readable. I took a read through and paged through the code on the new data model. https://code.blicky.net/yorhel/ncdu/src/branch/zig is the zig branch, which you can checkout or browse if you’re interested.

          3. 3

            nit: s/Zig 8.0/Zig 0.8.0

            1. 1

              Keep up. Been using this for many years and it’s great.