Mond_

6 ms·

31.
by Mond_ 6mo ago
really?
32.
by Mond_ 6mo ago
So, where can I buy a handful for personal use?
33.
by Mond_ 6mo ago
I think that a "minimal viable baseline" type implementation should not break the ODR. In Rust these types of proposals are common, in C++ less so. The incredibly tedious release process encourages everyone to put in just as much
34.
by Mond_ 7mo ago
Well, I've been unable to follow you as well, then. Obviously if they'd used a different type of syntax (e.g. using # for annotations), those would also be compatible with the language spec, and other implementations would still
35.
by Mond_ 7mo ago
It's an overloaded comment. I am personally quite fine with it, I don't think it's bad. but it is an overloaded comment.
36.
by Mond_ 7mo ago
This is begging the question. Yes, but why did they do that over dedicated syntax? (My personal theory is that early go had a somewhat misguided idea of simplicity, and preferred overloading existing concepts with special cases over intro
37.
by Mond_ 7mo ago
This is such a silly response when "You've gotten better at using them and know how to work around their flaws now." is right there and seems a lot more plausible.
38.
by Mond_ 7mo ago
Manjaro sells itself as "Arch, but more approachable". In reality, you'll often end up with "Arch, but with additional weird package management upgrade issues that are a byproduct of Manjaro's own repositories inter
39.
by Mond_ 8mo ago
I used Manjaro for a few years. That's how I learned a pretty important lesson about software engineering that still informs how I work to this day. "A layer of abstraction on top of a stateful legacy system often doesn't res
40.
by Mond_ 8mo ago
I think a lot of the really old school people don't care, but a lot of the younger people ( especially those disillusioned with C++ and not fully enamored with Rust) are in fact quite happy for C to evolve and improve in conservative,
41.
by Mond_ 8mo ago
The tradeoff Go made is that certain code just cannot be written in it. Its STD exists because Go is a language built around a "good enough" philosophy, and it gets painful once you leave that path.
42.
by Mond_ 8mo ago
Bad news, John Google told me they already quantized it immediately after the benchmarks were done and it sucks now. I miss when Gemini 3.1 was good. :(
43.
by Mond_ 8mo ago
OpenAI has a whole history of trying to scoop other providers. This was a whole thing for Google launches, where OpenAI regularly launched something just before Google to grab the media attention.
44.
by Mond_ 8mo ago
why call him that when "saltman" is right there
45.
by Mond_ 8mo ago
It's worth pointing out that the two examples that you're writing are actually strictly different, and not just "better syntax for the same thing". (This is assuming `String | Int` works as in Python, and the second exam
46.
by Mond_ 8mo ago
Sounds like it might be an issue with your setup, considering that other people have no problems running it. Hard to tell what the problem is, but definitely a frustrating situation.
47.
by Mond_ 9mo ago
I love how the haters of Rust's syntax can be roughly divided into two groups: (1) Why doesn't it look like C++? (2) Why does it look so much like C++?
48.
by Mond_ 10mo ago
Strong +1, Void Stranger is amazing and has a spiraling depth that just keeps going and going.
49.
by Mond_ 10mo ago
Interestingly, Google already donated its own AgentToAgent (A2A) protocol to the Linux donation way earlier this year.
50.
by Mond_ 10mo ago
Pixel hardware is below average? Since when? That sounds like a flagship phone to me.
51.
by Mond_ 10mo ago
Huh? Rust is just an example here. What I am saying is that you're just redefining float to mean NonNaNFloat. This is fine, I guess, but it will cause a bunch of problems since e.g. Division of two floats has to be able to return NaNs.
52.
by Mond_ 10mo ago
What exactly do you need that Zig doesn't have? Inheritance?
53.
by Mond_ 10mo ago
Meh, you also see algorithms that have subtle bugs because the author assumed that for every integer x, -x has the same absolute value and opposite sign. I view both of these as not great. If you strictly want to rely on wraparound behavior
54.
by Mond_ 10mo ago
This is a bit confused. You're saying `float`, but a float comes with NaN by default. Any float can take NaN values. If you actually want the compiler to check this on the level of the type system, it'd have to be `NonNaNFloat | N
55.
by Mond_ 10mo ago
Yes, and it's good that way. Please, anything but a dependency injection framework. All parameters and dependencies should be explicit.
56.
by Mond_ 11mo ago
What is wrong with that guy in the comments shouting? Christ on a stick, this is the worst crash out I've seen over something like this
57.
by Mond_ 11mo ago
> The fact is, Rust addresses only one memory safe thing, and that is double free. If you don't understand why that is, you probably shouldn't talk about memory safety. How does Rust not address use after free?
58.
by Mond_ 11mo ago
Pet peeves nitpick: it's not even a tuple. Go doesn't have tuples. It just has special-cased "multiple return values", which means that it's often impossible to just stuff the return of a function call (error value
59.
by Mond_ 11mo ago
No, I just don't think you have identified a problem in the first place. You've complained a lot, but you've not even been specific enough to point at a single concrete thing! You've been so lacking in specifics I don&#x
60.
by Mond_ 11mo ago
? Putting a program into a safe container or isolation boundary (this is roughly what GC is in this context) causes it to be memory safe. This is not an interesting observation. It also causes it to be significantly slower, to the point of

More ›