Take off every zig
this post was submitted on 05 Feb 2025
31 points (91.9% liked)
Technology
61456 readers
4085 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
All your base are belong to us
The creator of Zig is a dope dude, one of the best Killer Queen players to have played the game.
I often wondered why people gush over it, but never tried it myself. This is actually an article I wanted to read!
I'd never heard of it, and now I have, so this was the article I needed to read... apparently.
Great article I think. I don't have a lot of experience in zig, but I feel like it's just a better version of C. More specifically, C with a more modern synthax, better defined behaviour, better error handling. As the author highlights it, using the comptime and reflection to make generics can easily become a footgun and make the code messy. But hey, having the option to make generic code is still better than C.
Take this example for instance:
fn doMath(x: anytype) @TypeOf(x) {
// …
}
There is no way to know what that function requires as input.
Of course you can't know. That function has no requirements. As such there's only one thing it can do.... return x. Anything else is making an assumption about the parameter being passed.