noodledoodletwo

5 ms·

1.
by noodledoodletwo 4y ago
I recommend trying it again. Consider how old the language is, 7 years is a really long time ago. It may not be the smallest language, but, it compiles pretty tightly.
2.
by noodledoodletwo 4y ago
The productivity cost is mostly up front, once you understand borrowing it's seriously not bad in 99% of cases. Also, you can be initially productive in C or C++, but how much time goes into trying to fix undefined behavior, threading
3.
by noodledoodletwo 4y ago
I actually disagree with that and think it encourages bad practices in people who don't know better. The rise of fuzz testing on these old c applications following this kind of mentality is a constant source of cves . Why expose users
4.
by noodledoodletwo 4y ago
I'll believe it when I see it hit 1.0 and has a healthy user base.
5.
by noodledoodletwo 4y ago
It's really not that hard to use once you invest some time into it. I know where you are coming from, but appeasing the compiler actually means "I am writing safe code". Rather then "it compiled let's see what happe
6.
by noodledoodletwo 4y ago
What environment cannot run C?
7.
by noodledoodletwo 4y ago
Thanks for explaining, I really appreciate it.
8.
by noodledoodletwo 4y ago
Yea but for the most part you can avoid macros, and areas where you can't you can consider them to be keywords in my opinion anyways. Macros aren't all bad, but they do get abused a lot and make a nightmare for others. Fwiw Ive on
9.
by noodledoodletwo 4y ago
Fair enough thanks for explaining. Basically if you want to make your own Malloc or things like it, zig is friendlier. Will say though, I've used rust for gamedev, and found the experience to be really nice. Was I writing my own memcpy
10.
by noodledoodletwo 4y ago
See I got downvoted a bit... Let me rephrase, other modern languages offer something along the lines of these, of the things that aren't there for say rust, close integration with c/c++ is nice. Ie rust has nostd, etc.
11.
by noodledoodletwo 4y ago
Does a really short summary of this read kind of like, "zig is a modern c, but I like using rust as a modern c++"? Agree, Tokio is a little tricky for people new to rust no doubt, but it's tricky for a reason. It's savin
12.
by noodledoodletwo 4y ago
I see where you are coming from, zig is easier to learn, but zig doesn't offer what rust does with respect to safety. That feature is so hard for me to ignore. I respect it though, some people want to be up and running with a new techn
13.
by noodledoodletwo 4y ago
D nim and a few others offer nicer syntax over what's normally C for sure. Yea it doesn't surprise me that an established product had trouble incorporating rust, but at the same time, there's a reason why they went through wi
14.
by noodledoodletwo 4y ago
Yea I feel like most of these differentiators aren't things most people care about barring one. Tight integrations with c/c++ is potentially useful, beyond that I don't really get it. It's kind of like Hare in that regar
15.
by noodledoodletwo 4y ago
Cool article. I can't figure out why i am supposed to care about zig beyond it's fun? I get that it's interesting and more safe than C (honestly though what the hell isn 't). Say you write rust pretty regularly for new p
16.
by noodledoodletwo 4y ago
I agree with you all. Bake it into clippy or make a different clippy aka seclippy. Also, I appreciate the docs so I understand why with examples. Also make a attribute that blocks some of these things