joaofbantunes

joaofbantunes, 21 hours ago

Doesn't really affect me, I was already using it and other things from the all products pack, but find it nice anyway 🙂

Also, I didn't really actively advocate for it, I just used it, folks noticed it and tried for themselves. Now, here we are 😅

joaofbantunes, 21 hours ago

@khalidabuhakmeh didn't do anything though, but thought about sharing 🙂

joaofbantunes, 3 months ago

@khalidabuhakmeh /me mostly ignoring both 😅

joaofbantunes, 4 months ago

@khalidabuhakmeh inspired by this "back to basics" tip: don't call ToList/ToArray blindly everywhere, creating a crap ton of collection copies.

For example when R#/Rider warns about possible multiple enumerations of an IEnumerable, folks response to it is adding a ToList/ToArray in there, very likely, unnecessarily.

joaofbantunes, 5 months ago

@khalidabuhakmeh I haven't used attributes with EF Core in years. I rely on either language features or fluent configuration.

joaofbantunes, 5 months ago

@khalidabuhakmeh why would everyone be changing the configuration for an entity at the same time? 🙂

joaofbantunes, 5 months ago

@khalidabuhakmeh IEntityTypeConfiguration is your friend, or in this case, my friend 😅

joaofbantunes, 5 months ago

@khalidabuhakmeh

joaofbantunes, 5 months ago

@khalidabuhakmeh here it is

joaofbantunes, 5 months ago

@khalidabuhakmeh true. The code wasn't, at all, optimized for reading 😛

joaofbantunes, 5 months ago

@xoofx ah, didn't know about this method, will give it a try, thanks!

joaofbantunes, 5 months ago

@xoofx it's indeed the fastest approach from the ones I've tried. Allocates a bit more than the custom equality comparer, but overall, it's faster.

joaofbantunes, 5 months ago

@khalidabuhakmeh I can try, but I’m not a performance expert, just trying to implement something that doesn’t suck (too much 🤣)

joaofbantunes, 6 months ago

@khalidabuhakmeh @Moke only 3 months? 😅 I think I've been using it (in Rider) since March or something, when the first preview was made available 🙂

joaofbantunes, 6 months ago

@khalidabuhakmeh @Moke same. Unless there’s some issue that really blocks me, I’m always on EAP (and was always in Preview when I used VS).

joaofbantunes, 6 months ago

@khalidabuhakmeh while Aspire looks interesting, I feel like its usefulness scope is smaller than the #DotNet team thinks (or maybe I'm not the target audience).

Taking my current company as an example, even if we built all microservices with #DotNet (which we don't, we're polyglot), we don't spin up all of them locally at the same time, as they're developed in isolation.

Needing to spin up all the services locally smells like a distributed monolith 🤷‍♂️

joaofbantunes, 6 months ago

@khalidabuhakmeh the telemetry stuff still looks interesting though, even if developing a single service at a time

joaofbantunes, 6 months ago

@bjorkstromm @khalidabuhakmeh I also didn’t care much about Tye for the same reason. Sure, it can be useful for the dependencies, but not much else, and even then, I prefer something like Docker Compose as it’ll work for all teams, not just the ones working with .NET.

Now, given Aspire adds something more than just spinning up dependencies (i.e. telemetry), it can be worth a look, but even so, when you’re polyglot, you’re probably better off finding a solution that works for all teams.

joaofbantunes, 6 months ago

@khalidabuhakmeh @bjorkstromm I know, it’s just a matter of spinning up targets for the telemetry data locally. The Aspire thing is that the target and UI is built-in.