#zig101

1 messages · Page 1 of 1 (latest)

vagrant bear
#

I've been... I'll say "vocally" frustrated about how difficult it is to find good documentation and examples of basic tools in zig. I did some digging today, it seems that the zig.guide hasn't had a commit or any activity in 6 months. Ziglings is good and has been helpful. Still, most of the documentation is in the source code, especially tests, but also in version changelogs and sometimes the docs themselves if you already know enough to make sense of them. I'm generally proactive, so I decided to start writing a detailed beginner guide to get someone from zero to knowing enough to use most of the features of zig. I decided I was either going to quit and pick up rust or double down. So this project is me taking my time and answer all the questions I'll need answers to one at a time until I understand zig well enough to build real skills. I figure that documenting this process can be useful to other people. I expect to make mistakes, have difficulty, have explanations and implementations that could be better: in short, I'm saying I'll probably need help, and welcoming criticism/contribution. I think this could be good for me and make the language more accessible in general.

UPDATE:
In trying to write the guide I wish I had, I eventually found resources that did everything I wanted anyway. This is, in part, thanks to the fine ziggerydoos who reached out to help me. Thanks to all of you. I removed the public mirror, and while I will continue my guide in private just to track my progress and understanding, I am just going to link to some other projects that are both up to date and basically do exactly what I was aiming to:

https://zigbyexample.neocities.org/

https://pedropark99.github.io/zig-book/

#

Rn I would gladly welcome input regarding omissions, factual failures, and structure suggestions.

cedar comet
#

it may be useful to include a newline in the hello world example, as some coming from higher-level languages might not be aware for the need for one.

vagrant bear
swift barn
thin sky
vagrant bear
vagrant bear
#

...at least I got a decent markdown editor out of the deal. May or may not continue just so I can know I know what I'm doing, I'll have to think about it.

thin sky
#

😭 sorry

vagrant bear
#

Well, after some reflection I decided to scrap this guide. My goal was to create the docs I wish I had, and by doing the work I ended up finding what I needed. How I expected? No, but I am calling it a W

cobalt widget
swift barn
#

Reminds me of Andrew's blog, both need a little HTML course

unkempt falcon
vagrant bear
#

At least my version has dark mode. Lol.

swift barn
vagrant bear
swift barn
#

Ahh cool

#

It doesn't work

swift barn
#

It's similar to the Go one

#

Yours could be also added

#

I'd like it in PDF format somehow, since you are using Quarto

vagrant bear
#

It was a joke lol. Uh, the readme does link an html entrypoint if you really wanted to see what I had so far, it is not hosted anywhere yet and not quite ready for that. You'd either have to clone and open it in your browser raw or otherwise render the html from source atm

swift barn
#

I see

vagrant bear
# swift barn I see

I wasn't planning on continuing as I would be duplicating an existing project: Are you suggesting I should?

swift barn
#

I mean, on duplication sure, I guess contributing to the examples one might be useful, haven't really read any of those, but it's about whether it gives more value than the examples one. You have made it all already and used Quarto... So that's something the examples one doesn't have, a possible PDF output, Quarto being quite interactive too

vagrant bear
#

It would make me better at zig too, so there is that. thank you