🎙️🚀Get ready to explore the uncharted territories of .NET in the latest episode of "The Breakpoint Show" podcast! 🎧 In Episode 4, we'll be unraveling "The Missing Parts of .NET" 🕵️♂️🌐.
@breakpointshow Really interesting podcast, thank you! I have a few questions/thoughts about the last episode. 1. Do you think it might be better for dotnet to be the best choice for backend developers rather than spreading energy and time across different areas (e.g. ML, desktop, mobile)?
@breakpointshow 2. Maybe we don't have many open-source projects (as I've heard in this episode) because there aren't many big companies (except MS) that use dotnet and are ready to put effort into creating something new (like k8s came from Google)?
@breakpointshow What I personally miss is something like a "How to do it right in dotnet" guide. Which is better to use: controllers or minimal api? How to check for not-null: x!=null, x is not null, x is {}. When should I use anonymous objects, when tuples, when records, and when simple classes? And etc. So many choices
@khalidabuhakmeh@breakpointshow@cwoodruff@maartenballiauw In some cases you're definitely right. But how do you explain in a merge request that a tuple is more appropriate than a record in that particular case? If your colleague thinks otherwise and won't agree with you. At one of my previous jobs, we almost had a fight (that's not an exaggeration) over tuples.
But some folks only learn fire is hot when they get burned.
In your case, note the decision, measure the impact in production, and see if the choice has a considerable impact. If it does, then the person learns the lesson the hard way.
Working in teams isn't always about being right all the time. It's about moving everyone towards the right direction. Sometimes you need to take a detour. 😅
@rafaelldi This is just my opinion ( @cwoodruff), but I find that dotnet is a great general framework, but I find it strongest for backend work myself. I think dotnet could have a resurgence on the web front end by having a simpler path for 90% of the needed work for web dev. Maybe @maartenballiauw and @khalidabuhakmeh have their own takes.
#blazor hasn't been good for a web site experience compared to razor pages.
It's good for an app experience. I'd much prefer to build a call center app or order entry or other line of business scenarios with Blazor compared to razor pages.
And in most of those scenarios, seconds of app load each morning is irrelevant.
@rockylhotka@cwoodruff@maartenballiauw@breakpointshow@rafaelldi that's fair, and applying the tech matters for folks. Each team should evaluate it based on their needs. That said the hype-chamber can be strong in our ecosystem so it's hard to get an unbiased view of solutions sometimes.
Add comment