Need advice about which tool to choose?Ask the StackShare community!
.NET vs Symfony: What are the differences?
.NET: A free, cross-platform, open source developer platform for building many different types of applications. .NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more; Symfony: A PHP full-stack web framework. Symfony is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP. Symfony can be used to develop all kind of websites, from your personal blog to high traffic ones like Dailymotion or Yahoo! Answers.
.NET and Symfony can be primarily classified as "Frameworks (Full Stack)" tools.
"Tight integration with visual studio", "Stable code" and "Great community" are the key factors why developers consider .NET; whereas "Open source", "Php" and "Community" are the primary reasons why Symfony is favored.
.NET and Symfony are both open source tools. It seems that Symfony with 21.1K GitHub stars and 7.01K forks on GitHub has more adoption than .NET with 11.1K GitHub stars and 2.4K GitHub forks.
According to the StackShare community, .NET has a broader approval, being mentioned in 1566 company stacks & 239 developers stacks; compared to Symfony, which is listed in 374 company stacks and 277 developer stacks.
I was considering focusing on learning RoR and looking for a work that uses those techs.
After some investigation, I decided to stay with C# .NET:
It is more requested on job positions (7 to 1 in my personal searches average).
It's been around for longer.
it has better documentation and community.
One of Ruby advantages (its amazing community gems, that allows to quickly build parts of your systems by merely putting together third party components) gets quite complicated to use and maintain in huge applications, where building and reusing your own components may become a better approach.
Rail's front end support is starting to waver.
C# .NET code is far easier to understand, debug and maintain. Although certainly not easier to learn from scratch.
Though Rails has an excellent programming speed, C# tends to get the upper hand in long term projects.
I would avise to stick to rails when building small projects, and switching to C# for more long term ones.
Opinions are welcome!
Decided to change all my stack to microsoft technologies for they behave just great together. It is very easy to set up and deploy projects using visual studio and azure. Visual studio is also an amazing IDE, if not the best, when used for C#, it allows you to work in every aspect of your software.
Visual studio templates for ASP.NET MVC are the best I've found compared to django, rails, laravel, and others.
Pros of .NET
- Tight integration with visual studio260
- Stable code249
- Great community179
- Reliable and strongly typed server side language.170
- Microsoft131
- Fantastic documentation107
- Great 3rd party libraries81
- Speedy70
- Great azure integration64
- Great support56
- Highly productive24
- Linq23
- High Performance22
- Great programming languages (C#, VB)21
- C#19
- Open source18
- Clean markup with razor12
- Powerful Web application framework (ASP.NET MVC)12
- Powerful ORM (EntityFramework)12
- Fast10
- Constantly improving to keep up with new trends8
- Visual studio + Resharper = <38
- Dependency injection7
- TFS6
- Job opportunities5
- High-Performance5
- Integrated and Reliable5
- Security5
- Huge ecosystem and communities5
- Light-weight5
- Lovely4
- Variations4
- Useful IoC3
- Scaffolding3
- Asynchrony3
- Concurrent3
- Support and SImplicity3
- {get; set;}3
- Default Debuging tools2
- Entity framework2
Pros of Symfony
- Open source167
- Php139
- Dependency injection122
- Community121
- Professional114
- Doctrine74
- Organized66
- Modular architecture62
- Smart programming42
- Solid38
- Documentation14
- LTS releases11
- Robust6
- Easy to Learn6
- Good practices guideline5
- Bundle5
- Decoupled framework components5
- Service container4
- Simple4
- Powerful2
- Flexible1
Sign up to add or upvote prosMake informed product decisions
Cons of .NET
- C#9
- Too expensive to deploy and maintain9
- Microsoft itself7
- Microsoft dependable systems5
- Hard learning curve3
Cons of Symfony
- Too many dependency9
- Lot of config files7
- YMAL3
- Bloated1
- Feature creep1