Mond_

6 ms·

91.
by Mond_ 1y ago
I mean, I don't want to be a "Keeps bringing up Rust in the comments" sort of guy, but null pointer dereferences are in fact a problem that can be solved essentially completely using strict enough typing and static analysis.
92.
by Mond_ 1y ago
I really don't like how this article claims that the primary issue with Go's error handling is that the syntax is too verbose. I don't really care about that. How about: - Errors can be dropped silently or accidentally ignore
93.
by Mond_ 1y ago
HoTT is a highly technical, highly niche topic and it doesn't make sense to tackle two ambitious projects at the same time like this. HoTT isn't even remotely close to being accepted as a reasonable standard, and it's kind of
94.
by Mond_ 1y ago
This isn't much of a tutorial or learning guide, it's a lookup table that roughly pattern matches C++ to Rust. Probably not the best place to start learning.
95.
by Mond_ 1y ago
How would you deal with fallible construction of objects while avoiding exceptions in idiomatic C++?
96.
by Mond_ 1y ago
You cannot possibly know which innovations and standardizations happened past 1982 in the world in which Bell was not dismantled.
97.
by Mond_ 1y ago
Could it be? Is it time? Is it finally the year of the Linux desktop?
98.
by Mond_ 1y ago
Cool as fuc + very nice blog design.
99.
by Mond_ 1y ago
Guilty as charged, I did not know about the `import_trait_associated_functions` feature at the time. I might add a note to the article to clarify this.
100.
by Mond_ 1y ago
There's like 5 terms for this in different programming languages. I think 'pipelining' is the best universal word. 'Method chaining' just isn't correct, nor is 'builder pattern', and 'transducer&
101.
by Mond_ 1y ago
Yeah, I really wanted to avoid a discussion over functional vs. imperative programming, so I just... didn't talk about the imperative style at all, and just said so in the first section. I think the imperative style isn't as reada
102.
by Mond_ 1y ago
Point free was technically mentioned once, but more as a "I'd rather not get into this in great detail right now." thing. It's really cool, though.
103.
by Mond_ 1y ago
Have you read the article? This isn't about functional vs. imperative programming, it's (if anything) about two different ways to write functional code.
104.
by Mond_ 1y ago
Oh, interesting! Thank you, I did not know about that, actually.
105.
by Mond_ 1y ago
That'd be problematic, but also sounds like a (solvable) tooling problem to me.
106.
by Mond_ 1y ago
I feel like a sufficiently good debugger should allow you to place a breakpoint at any of the lines here, and it should break exactly at that specific line. fn get_ids(data: Vec<Widget>) -> Vec<Id> { data.iter()
107.
by Mond_ 1y ago
"These are the same picture." (Sort of.)
108.
by Mond_ 1y ago
Does it actually make more sense, or is it just more familiar?
109.
by Mond_ 1y ago
> The second approach is open for extension - it allows you to write new functions on old datatypes. I prefer to just generalize the function (make it generic, leverage traits/typeclasses) tbh. > Probably for lack of > weird o
110.
by Mond_ 1y ago
> if your language allows you to implement proper pipelining with implicit argument passing by yourself > You can decide for yourself what symbols are used and what you find intuitive i mean this sounds fun but tbh it also sounds like
111.
by Mond_ 1y ago
> Pipelining can become hard to debug when chains get very long. The author doesn't address how hard it can be to identify which step in a long chain caused an error. Yeah, I agree that this can be problem when you lean heavily into
112.
Pipelining might be my favorite programming language feature(herecomesthemoon.net)
372 points by Mond_ 1y ago|348 comments
113.
by Mond_ 1y ago
No need to kick someone while they are down.
114.
by Mond_ 2y ago
The Llama 4 launch looks like a real debacle for Meta. The model doesn't look great. All the coverage I've seen has been negative. This is about what I expected, but it makes you wonder what they're going to do next. At this
115.
by Mond_ 2y ago
Do you have a source for this? That's interesting (if true).
116.
by Mond_ 2y ago
> The coolest one I've heard is that Fuchsia's network stack managed to eliminate deadlocks. Is there a write up on this? That's very cool
117.
by Mond_ 2y ago
No smallcaps variant? Disappointing honestly.
118.
by Mond_ 2y ago
Google is worse at marketing and hyping people up.
119.
by Mond_ 2y ago
Pretty sure the modern Gemini image models can already do token based image generation/editing and are significantly better and faster.
120.
by Mond_ 2y ago
Seems like a perfect fit for C, and glad to see we're trying to avoid stepping into that funny pitfall Go has with its function-scoped defer keyword. Glad to see C is evolving and standardizing.

More ›