@scottsantens@Kekius_Sage UBI is the only logical end state. Unfortunately, I predict that the powers that be will milk the current system until the point where life is uncomfortable enough for a mass uprising or there are simply not enough consumers participating in the economy for profitability.
I had an interesting discussion with the guy who came to clean my dryer vent. His last job was building a chimney. When I told him I was a SDE, he asked if I was afraid of AI. I said “Would you like me to dictate to you how to build a chimney based on Google searches?”
@JessicaValenti The GOP’s thirst for low-cost worker bees with no prospects is unquenchable! I wonder if there’s a book that would say what they’re doing is evil? 🤔🤔✝️
𝟱𝟬% 𝗼𝗳 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗳𝗮𝗰𝗲𝗱 𝗺𝗲𝗺𝗼𝗿𝘆 𝗹𝗲𝗮𝗸𝘀 𝘄𝗶𝘁𝗵 𝗘𝗙 𝗖𝗼𝗿𝗲
They're making the same mistake 👇
❌ Improper handling of DbContext lifetimes.
Many devs simply register DbContext as scoped and call it a day. ▶️
But reality is often more complex.
DbContext isn't thread-safe — sharing it across threads will cause exceptions.
It's lightweight and meant to be short-lived, instantiated frequently, and disposed properly.
❌ Improper handling leads to growing memory usage and eventual leaks.
Thankfully, EF Core provides solutions to handle complex scenarios:
↳ 𝗜𝗗𝗯𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝗙𝗮𝗰𝘁𝗼𝗿𝘆
Allows safe, on-demand creation of DbContext instances — perfect for background tasks, multi-threading and desktop applications.
↳ 𝗗𝗯𝗖𝗼𝗻𝘁𝗲𝘅𝘁 𝗣𝗼𝗼𝗹𝗶𝗻𝗴
Reuses pre-configured DbContext instances to minimize performance overhead.
Pooling resets contexts after use, significantly cutting down memory and CPU waste.
↳ 𝗣𝗼𝗼𝗹𝗲𝗱 𝗗𝗯𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝗙𝗮𝗰𝘁𝗼𝗿𝘆
Want the best of both worlds? Combine DbContextFactory with Pooling — Pooled DbContextFactory.
You get on-demand contexts that are efficiently reused, optimizing your app's performance.
✅ Always dispose contexts promptly—either with using statements or returning them to the pool.
✅ Never share DbContext across threads.
Proper lifecycle management boosts application stability, responsiveness, and scalability.
Understanding these nuances can eliminate those sneaky memory leaks that plague many EF Core projects.
Here are 10 more mistakes developers make in EF Core:
↳ https://t.co/dViwIG2xOc
——
♻️ Repost to help others avoid memory leaks in EF Core
➕ Follow me ( @AntonMartyniuk ) to improve your .NET Skills
Here’s some CoPilot features I’d like to see integrated in @VisualStudio:
- Keystroke to type a prompt & have it generate code in-line
- Keystroke to have CoPilot generate XML comments (without having to explicitly ask)
- “Apply” button at bottom of reposes as well as the top
@mkristensen Hi! Here are a couple of things I'd really like in VS:
- When adding a watch when debugging, I'd like Intellisense to autocomplete and show me the available fields & properties when I type "."
- In addition to "Find all references": "Find Assignments" + "Find Gets"
@NealCuliner@mkristensen Getting anything working in Rider is a real pain, though. Everything source control just seems to just work seamlessly OOTB in VS
@Ifindjewtards@FrankAtHPP@VEsoterica It’s apples & oranges because the 32X was an intermediate upgrade to a platform in deep decline, while the PS5 was a full generational leap, following up a platform that was still going strong
@Voultar You’re like a member of the party fighting Zeromus at the end of FFIV. He keeps hitting you with Big Bang, but you keep getting back up after some Curaja from Rosa!