A LINQ predicate in the Azure Service Bus receiver created a delegate on every call. A loop removed it. Going further helped some inputs and hurt others.
What I learned from the generated code:
https://t.co/2iJAKxq87x
#dotnet#csharp
`pi-emphasis` is my favorite extension I've built in a while.
This works great for _me_, but if you hate it, remember that terminals can render pretty much anything. So get creative and use your imagination.
https://t.co/QTMODJ3FhW
When I heard about reverse-engineered PS5 games, I thought it should be doable for MS-DOS demos too. And while I'm at it, improve the graphics a bit.
The first is 303 by Statix (@mmalex), and next up is his Paper 64k, with which Statix crashed my hard drive at Wired. Fun times and good memories! ;-)
https://t.co/6nusvGT8MX
@Aaronontheweb Did you get demand for it? Why are you trying to compete in this crowded space? Is this model something your customers need besides actors?
Just posted my talk from last Friday, "You Should Be Using IAsyncEnumerable," on @petabridge 's YouTube channel: https://t.co/cUBSX49kHl
Give it a watch and leave a comment. Let me know what you liked and what we could do better too
@Aaronontheweb@petabridge Great talk! One thing that could have been addressed was the bridge from tasks with the When any in a loop which is a poor people version of a fake stream.
@danielmarbach That maintainer question is the useful part. In business code I'd take the more complex version only when a benchmark backs it and the PR links to it. Otherwise the next person simplifies it back without knowing why it was there 😅
@dadhi@DanJSiegel@Aaronontheweb Sometimes yes but I'm shared code bases not everyone has the same level of experience, expertise or whatever so complexity is also in the eye of the beholder. I've said "this is simpler" many times and got blank stares back 🤣
I learned .NET performance by sending PRs to the Azure SDK. The rejected ones taught me the most, because a maintainer would ask: is this complexity worth it?
New series on what I picked up, starting with when to bother at all.
https://t.co/aKtccAXexl
#dotnet#performance
@danielmarbach Absolutely 🙂 And since we've already been talking on LinkedIn, I know we're looking at a similar underlying problem from pretty different architectural angles. Same goal in many ways, different layer and approach. I think that's a good thing.
I tried every harness under the sun and always circle back to @pidotdev.
Many offer good features, but it's all or nothing. I can’t cherry-pick what I like.
It is less effort to customize Pi, then spend time circumventing workflows that don’t fully match my needs.