zerofan

7 ms·

1.
by zerofan 10y ago
Not a very civil tone. Just go ahead and ban my IP or something... I'm not particularly interested in appeasing you.
2.
by zerofan 10y ago
You seem like a forthright person, but with or without metaphors, we're still talking past each other. My point about remote exploits, airplane crashes, and cops is not about me. Yes, public facing software needs to be careful, but (f
3.
by zerofan 10y ago
> > The city I live in now has many bike paths, completely separate from major roads. > Which wasn't the point of that at all. It was to point out that you[r] assessment of how much time is wasted working around problems in ea
4.
by zerofan 10y ago
I think you have an inconsistent threshold for civility. The post I replied to had it's fair share of snarkiness, insincerity, exaggerations, and patronizing.
5.
by zerofan 10y ago
> I could visit a country with a completely different set of laws regarding driving [...] Arguments by metaphor aren't my thing. It's very likely I would become more proficient at Rust if I programmed in it more. It's al
6.
by zerofan 10y ago
To me, Rust's &str seems a lot more like const char* (with a size tacked on for bounds checking). But you're the expert, so if I did agree they were the same, then C++ adopting it in the STL is practically proof it's a m
7.
by zerofan 10y ago
> There are two string types in Rust, `String` [...] Anything else is just a shim for FFI. I guess I don't have to worry about the non-Scotsman strings then... You've heard the criticisms about Rust's strings before, and
8.
by zerofan 10y ago
There are many things you could dismiss as style issues, but here is one relating to performance. Rust does not (yet) have integer generics. If I use Eigen (the C++ library), I can declare a matrix of size 6x9 and have the allocation live
9.
by zerofan 10y ago
Sorry, next time I'll say something like "If you're going to misrepresent his intention" so as not to confuse a quoted sentence. And I won't use the word "say", because clearly nobody says anything in a t
10.
by zerofan 10y ago
I don't believe those clever things are necessary for safety or performance. I think many of them are incidental and caused by a lack of taste or just a disregard for the value of simplicity. Rust deserves credit for it's good i
11.
by zerofan 10y ago
'everybody knows' red meat is bad?
12.
by zerofan 10y ago
I would prefer a surgeon who washed his hands over one who didn't but gave me antibiotics. I've had stitches a few times, but only one real surgery. I never got antibiotics for any of those. Maybe we could skip the analogies?
13.
by zerofan 10y ago
> I think it's more like: since you know the compiler won't let you write a buffer overflow, use-after-free, data race, etc., you no longer have to waste time worrying about whether your code might contain such problems, which
14.
by zerofan 10y ago
> I think it's a misconception to classify type-safety and memory-safety techniques as 'clever' I didn't call Rusts type-safety of memory-safety clever. The clever stuff is lifetime specifications, a multitude of s
15.
by zerofan 10y ago
Fair enough. I'm sorry about calling you out on the metaphor. Instead I'll call you out on the point itself :-) > Having safety features that you know you can rely on allows you to take risks that you normally wouldn't i
16.
by zerofan 10y ago
Please don't get me wrong - I would take safe over non-safe if everything else were equal. It's just that Rust made many other choices that are worse for me than what's in C++. Also, I think it would be very painful tryin
17.
by zerofan 10y ago
> > I think the safety aspect of Rust appeals to a lot of beginning programmers. > Is that a bad thing? The appeal to beginners is fine, maybe even a good thing, but the condescending comments from beginners is a lot like listening
18.
by zerofan 10y ago
If you're going to put words in his mouth, you should make them much stronger words. It's not a valid argument either way, but it'll seem more dramatic. (He didn't say either of your quotes...)
19.
by zerofan 10y ago
Have you done much skydiving? I used to go three days a week, for a couple years, between 4-10 jumps a day at a place that had world class experts. My experience is that only beginning skydivers are constantly preaching safety. They go a
20.
by zerofan 10y ago
Yes, the dot operator is a headache. As soon as you march down the road of a precompiler, you're off to building a new language. I think C++'s grammar is too much of a mess to just tweak the parse tree reliably. I suspect there
21.
by zerofan 10y ago
Version: rustc 1.13.0 (2c6933acc 2016-11-07) I remember installing it by cut and pasting one of the "curl ... | sh" commands there. > Nothing about that code should be doing bounds checks, as it's just allocating an array
22.
by zerofan 10y ago
I looked briefly at your code. I don't believe it is possible to be compatible with the STL and safe in the way the Rust guys intend. I might be wrong though. What happens with your vector in this code? using namespace mse::mst
23.
by zerofan 10y ago
> It compiles and runs effectively instantaneously for me on Ubuntu under Windows as well, so that's very strange. Maybe file a bug? Follow-up: I tried it with -O (don't know why I didn't think of that earlier), and it ru
24.
by zerofan 10y ago
I've written this several times in several ways using C++ (and I'll probably write it at least once more to make it better). In an early version I used an integer level as you came to, but it made the compiler very unhappy as it
25.
by zerofan 10y ago
I'm interested too. I've been thinking about the idea, and it seems like you'd have to be sure to re-use the hell out of your file descriptor on /dev/zero (otherwise, you could easily run out of file descriptors).
26.
by zerofan 10y ago
> That's true except our 16 bit support is nonexistant at the moment :) If you pay attention to your usage statistics, I'll bet you drop 32 bit support before the May 2025 deadline we were discussing in the other thread.
27.
by zerofan 10y ago
> basically no numbers in real world programs weren't constrained, it was often tests, toy programs The fact that C and C++ compilers generally chose to leave int at 32 bit on 64 bit platforms, combined with the standards requirin
28.
by zerofan 10y ago
> It's been around for roughly six or eight already, depending on how you count. I don't think you get to play on both sides of that fence. Some of your team has been working on Rust for that long, but I doubt any code with si
29.
by zerofan 10y ago
> How would you have gone about making Strings be "as comfortable as integers"? I would prefer a str be a str be a str, regardless of how you got it. Lowercase type-name and fundamental like an integer. I'm fairly certain
30.
by zerofan 10y ago
I'd like to see if Rust is still around in 10 years and then look before we declare the winner on this.... All software has bugs.

More ›