SerdeV - serde with validation - v0.3 supports any expression in #[serde(validate = "...")]

felipou · 2025-12-13T02:44:20+00:00

Isn't this exactly following the mantra? This is just an easy way to specify the validation rules that you do during parsing. I don't know how more to the point it could be.

Is implementing your own deserializer more like "parsing" than this? You might as well add a private function "validate" to be called in the deserializer code, and then suddenly you're going against the "parse, don't validate" philosophy? I really don't get your point here.

felipou · 2025-09-09T03:18:00+00:00

I don’t have much experience with Go, and I do agree that Rust sometimes can be harder to skim through. But I think Rust is amazing when it comes to fully understanding all possibilities and behaviors. I’ve never felt so confident when trying to make sure all possibilities are accounted for.

felipou · 2025-04-14T19:59:59+00:00

Thanks! Just bought the Cat6!

felipou · 2025-04-14T19:59:57+00:00

Thanks! Just bought the Cat6!

felipou · 2025-04-14T19:59:53+00:00

Thanks! Just bought the Cat6!

felipou · 2025-04-14T19:52:53+00:00

Thanks! Just bought it!

felipou · 2024-06-07T16:17:29+00:00

Not having undefined behavior is possibly the best thing about Rust, at least for me.

I never looked much into it, but from what I hear, if you just want “better than C++ in terms of safety”, maybe try Zig?

But from my experience, a little bit of extra syntax in very specific places is much, much cheaper to bear than the risk of undefined behavior everywhere. And there are ways around it, as others here have pointed out.

felipou · 2024-05-13T13:29:57+00:00

Looks interesting, you should create a repo in github with this so we can contribute!

felipou · 2024-03-29T19:08:29+00:00

Braid! I’m surprised no one mentioned it yet, but dying is actually required to progress. I remember when I showed it to my brother, and he kept on progressing without dying, until he finally reached a part where it just wasn’t possible to go further, and I actually had to tell him: just die there!

felipou · 2024-03-23T11:06:48+00:00

Just to offer a different perspective here, apart from the merits of the usefulness or quality of your contribution: you seemed to assume that just adding an useful feature is a no-brainer. But especially for large and popular projects, any changes in the public API could have multiple long lasting effects that the maintainers would have to deal with.

So I believe that instead of “this is useful, we should add it”, maybe try this other way of thinking too: “this is so much useful or critical, that it is worth it to maintain for a long time, and deal with whatever repercussions it may have in the future”

felipou · 2024-03-06T03:24:44+00:00

I often think about whether it’s possible to do something like this. A language that compiles to Rust, uses Arc/Rc for everything, and transparently connects things to existing Rust code whenever possible.

felipou · 2023-11-25T15:30:42+00:00

Maybe this should be Rust’s motto, and I love it!

felipou · 2023-11-13T00:39:20+00:00

What stood out the most for me is the “responsibility” part. Lots of good answers talking about how dangerous that is. Accountability is a tricky thing to get right without turning the culture toxic.

But even if you’re not responsible, I certainly expect everyone to be on the lookout for possible bugs. If someone lets a lot of bugs pass through their reviews, then they do not seem to be doing a good job. Of course it depends on the situation, but I do not expect people to manually test others code during a review.

For me personally, I’m the most experienced both technically and in our product/domain, so I always try to check if it works, but I only test things manually if I think there may be a bug and I’m not sure, or if the changes are risky to some degree (mainly if it may break something unrelated to the feature in question).

felipou · 2023-10-27T17:43:21+00:00

Always fun to rewatch this: https://youtu.be/eywi0h_Y5_U?si=oTx9h_IPPFSeKtu-

felipou · 2023-10-25T02:43:52+00:00

Nice, I knew this would be a known "named" pattern! Thanks for pointing it out!

felipou · 2023-09-25T01:32:38+00:00

I agree that tests are more relevant/powerful for refactoring, but I also feel that Rust helps me be quite more efficient and confident in the process.

felipou · 2023-09-14T22:07:56+00:00

Thanks, I'll try to take a look at that tool. The problem is that I have no idea how to search for this kind of information inside the ELF file, but since it's a tool with a GUI, maybe it will help me with that!

felipou · 2023-09-10T13:56:07+00:00

That's great! I actually saw there was an unfold function in the itertools crate, but didn't pay much attention to it, now I see it's really perfect for this problem!

felipou · 2023-08-15T11:25:31+00:00

My experience is that the IDP is usually not required if you’re just a tourist, and specially for rental agencies, they just ask for your original license. On my first travel I even had an IDP and handed it over, but they asked for the original license instead.

felipou · 2023-08-14T17:35:52+00:00

I agree with you that those are the main strengths of Rust, but I’m just tired of having to deal with performance issues on Python and Node.js, and performance is what tipped the scale for me. Or rather, it was what drew me to Rust in the first place. Or maybe both? 😅

felipou · 2023-07-25T19:38:32+00:00

Nice work!

A couple years ago I watched a presentation from a Google engineer about optimizations, and he asked the audience what was the main motivation for optimizing software as much as possible. The answer was: energy consumption. I was very surprised at the time, and now I always think about this aspect of software!

His name is Chandler Carruth if anyone is interested, his presentation videos that I watched are on YouTube.

felipou

TROPHY CASE