My guess is that it is about the language tooling, but it would be nice to hear from the authors themselves.
Game Jam 2 Results
11–20 of 193 posts
Re: Game Jam 2 Results
#12Earlier quoted context omitted.
For me Rust is a language that I would absolutely love to work with in a professional context. The type system and borrow checker have your back and help you make changes to the code without fear of accidentally introducing any regressions. For private lone-hacking projects though it feels way too complex and opinionated. Here Zig definitely gets closer to what I need, though sadly it made unused variables an compile…
I never understood this attitude, it's not like commenting out variables is difficult.
Commenting out a few variables isn't always easy either. Every try to add const to a legacy C++ project - it can take days to fix all the errors resulting from adding const to something that clearly is const in usage. I don't know zig, but I wouldn't be surprised if sometimes you get into this type of situation in a large code base (does anyone have a very large code base in zig yet?)
Re: Game Jam 2 Results
#13Re: Game Jam 2 Results
#14Earlier quoted context omitted.
>it's not like commenting out variables is difficult. But if you comment var A that uses var B now B is unused and you need to commnet B, but now B was using a function parameter C and this param is unused now so you need to update the function signature (I do not use Go,Zig so maybe they did not forced you to also use all the function params my experience is with linters where ehwn you comment something then more un…
Wow sounds like you really need to clean up your codebase. Seriously, I have never had this problem while coding in Go, and I'm a very very sloppy coder.
In any moderately complex function you'll have more than one expression, and those can depend on each other. And you want them to be named and assigned; it makes it easier to read and decode intent and debug things (unless you're one of those wizards who get it right on the first try every time, kudos to you then). I'd not approve a PR that inlines/embeds complex concepts within larger expressions just to avoid creating variables...
Edit: typos
Re: Game Jam 2 Results
#15Re: Game Jam 2 Results
#16Zig is not mentioned until the section "Programming languages" (including not being mentioned in the original title): please fix the title so as not to put too much focus on that.
Re: Game Jam 2 Results
#17WASM-4 seems to be a technically limited "console" (64kb of RAM, 160x160 console), so it's even more of a niche than just doing game dev for WASM.
Re: Game Jam 2 Results
#18Earlier quoted context omitted.
Thanks for sharing. Going to enjoy some time with Spark2014. OT: Searching for Spark2014 brings up a lot of results about the 2014 Chevrolet Spark. A shit box of a car of there ever was one.
Hah, Chevy Spark, and it's a gasoline car! I usually put "SPARK2014 programming" or "SPARK2014 Ada" in my searches. I used to get annoyed by all of the Apache Spark stuff that came up, but that seems to have waned a bit this past year or two. Vermont Technical College (VTC) used SPARK2014 to program their CubeSat and the book, "Building High Integrity Applications with SPARK"[1] is a great intro to it in a nice conte…
In fact, I guess in gas cars sparks are "better" since they are engineered in, and doing useful work.
Re: Game Jam 2 Results
#19Earlier quoted context omitted.
Wow sounds like you really need to clean up your codebase. Seriously, I have never had this problem while coding in Go, and I'm a very very sloppy coder.
What are you talking about? I don't understand how you've never encountered variables depending on each other. In any moderately complex function you'll have more than one expression, and those can depend on each other. And you want them to be named and assigned; it makes it easier to read and decode intent and debug things (unless you're one of those wizards who get it right on the first try every time, kudos to you…
Re: Game Jam 2 Results
#20Earlier quoted context omitted.
I never understood this attitude, it's not like commenting out variables is difficult.
It isn't difficult, but it is friction. You hit compile and a few seconds later you get an error that is unrelated to the change you wanted to test. I agree with all those errors once those changes are for production, but sometimes I wish the compiler would just shut up and let me test the actual change I just made to ensure it works. Commenting out a few variables isn't always easy either. Every try to add const to…
Only until getting rid of unused variables becomes a habit before you hit the compiler. Which is a good habit to have anyway.