81–90 of 193 posts
From the perspective that development time is a big constraint in a game jam it's no wonder zig is more popular than rust
I never got my rust wasm build to work without needing JS.
So.. good for prototyping, like Ruby?
Earlier quoted context omitted.
How long till we start complaining that Zig followers are cult like? Asking as Rustecean.
I've noticed people that like writing code in Zig are fans the language and the people that like writing code in Rust center their identity around the language. The former leads to people saying they enjoy writing code in Zig, the later leads to religious zealotry and moral condemnation for using anything other than Rust.
Earlier quoted context omitted.
> It isn't difficult, but it is friction. Only until getting rid of unused variables becomes a habit before you hit the compiler. Which is a good habit to have anyway.
Good habit, maybe, but it shouldn't cause a compilation failure. Add to that the snowball effect: you comment out a variable, compile, and you get another error because commenting out variable a made variable b unused. Rinse and repeat. It's a huge and totally unnecessary time sink. It should be opt-in, so that it's a warning by default, and then, when I'm ready to push my code, I could run some --strict mode that wo…
That eliminates the unused chain problem. Not sure if zig included that part of the feature as well.
Generally I agree though. The main problem with forcing unused variables, imo, is that it forces you to think a certain way. When I'm exploring the solution space on something, those constraints feel inhibiting.
Earlier quoted context omitted.
Arguably Zig is a better fit for game dev. At the high end game dev is all about memory layouts and cache optimization, and that goal can run counter to Rust's approach to memory safety.
Memory safety isn't in conflict with low-level control over memory layout.
So basically rust imposes a lot of limitations on how you can structure your program relative to something like Zig or C.
Earlier quoted context omitted.
I've noticed people that like writing code in Zig are fans the language and the people that like writing code in Rust center their identity around the language. The former leads to people saying they enjoy writing code in Zig, the later leads to religious zealotry and moral condemnation for using anything other than Rust.
Which language is the one where you make sweeping generalizations?
Instead of focusing on tradeoffs they chose to call others irresponsible.
Earlier quoted context omitted.
Zig is the new HN clickbait, taking over Rust's spot. That's a good sign for the language, honestly
Good sign for the language, bad sign for HN. I totally get it's nicer than C, I love it too, but it's completely irresponsible to push a language without a memory safety story, in 2022, this hard. From that relatively obvious conclusion it devolves into tedious nerdsnipes. Yes there are edge cases.
Earlier quoted context omitted.
That's the one thing keeping me from considering Zig for new projects right now. If some enterprising young developer is reading this and wants to make a name for themselves, you should fork the Zig compiler and change those errors to warnings. It would be an extremely popular project. EDIT: I'll even give you a catchy project name. Wig: Zig with Warnings
You should also consider that optimizing for incorrectness and prototyping speed might not be the professionally responsible choice in 2022.
I can only see downsides and no upside in this design. Why would you slow down the development workflow for something any decent compiler will discard as basic optimization step? It's an error about something that has absolutely no impact on the resulting program and its execution, you can probably find a dozen better reasons for Zig to throw errors where it doesn't.
Earlier quoted context omitted.
Which language is the one where you make sweeping generalizations?
It's funny you say that when a rustacean just posted below that it is irresponsible to use unsafe languages. Instead of focusing on tradeoffs they chose to call others irresponsible.
Earlier quoted context omitted.
How long till we start complaining that Zig followers are cult like? Asking as Rustecean.
I've noticed people that like writing code in Zig are fans the language and the people that like writing code in Rust center their identity around the language. The former leads to people saying they enjoy writing code in Zig, the later leads to religious zealotry and moral condemnation for using anything other than Rust.
However, what I've seen in the discourse of several programmers that claim to prefer Zig is the assumption that Rust is "not really that big of a deal". There's a constant minimization of the advancements both the ownership system and the safety approach provide, and a lack of recognition for the fact that the language is a "game changer" in the industry.
Overall, this looks a lot like rationalization of an emotional choice, which for me is much more close to religious zealotry.