I was scrolling through Facebook when I found a post by She Explores Data about using Python to solve everyday programming problems.
Messy data? There is a library for that.
Need automation? There is a tool for that.
Building an API? Yes, that too.
My brain says: nice.
My .NET brain says: wait, what about us?
Then I generated an infographic, this time about using .NET 10 for problem-solving.
Start with the problem, not the package
Sometimes I open NuGet before I have properly understood the task.
"This package looks useful."
"That one has lots of downloads."
"Maybe I should install both. Just in case."
Now I have more dependencies.
Still the same problem.
(more packages, but you still haven’t solved the original problem:))
What I liked about these graphics is the simple approach: start with what you need to build, then look for a tool that fits.
A little .NET toolbox
Here are some starting points from the .NET graphic, in my own words:
This is a starting list, not an instruction to install everything.
Also, the infographic focuses on .NET 10. If your project targets another version, check the framework requirements and package compatibility first.
Not Python versus .NET
I do not read this as a language competition.
Python has a rich ecosystem, especially for data work and automation. .NET has plenty of options for applications, services, and other workloads too.
The useful question is not:
"Which language wins?"
It is:
"Which tool fits this problem, this project, and this team?"
Sometimes the answer is Python.
Sometimes it is C#.
Sometimes it is a small script, not a whole new architecture.
Inspiration and credit
- Inspired by the She Explores Data Facebook post, "24 Python Problems and the Tools That Help Solve Them": https://www.facebook.com/share/p/1GJPGLaMse/
This article shares my own reaction to the Python post and the .NET infographic I created from that inspiration.
Love .NET!
Top comments (0)