Need advice about which tool to choose?Ask the StackShare community!
.NET vs Laravel: What are the differences?
What is .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.
What is Laravel? A PHP Framework For Web Artisans. Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.
.NET and Laravel can be categorized as "Frameworks (Full Stack)" tools.
"Tight integration with visual studio", "Stable code" and "Great community" are the key factors why developers consider .NET; whereas "Clean architecture", "Growing community" and "Composer friendly" are the primary reasons why Laravel is favored.
.NET and Laravel are both open source tools. It seems that Laravel with 53K GitHub stars and 16.2K forks on GitHub has more adoption than .NET with 11K GitHub stars and 2.37K GitHub forks.
Stack Exchange, Starbucks, and Docplanner are some of the popular companies that use .NET, whereas Laravel is used by PedidosYa, Sellsuki, and Webedia. .NET has a broader approval, being mentioned in 1561 company stacks & 231 developers stacks; compared to Laravel, which is listed in 817 company stacks and 753 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!
I am planning to develop project management system SAAS based. Can any one help me with selection of platforms from Django or Laravel and for database MongoDB or Firebase/Firestore or MySql? On front end I am going to use Quasar Framework (VueJS). Note : project will be Webapp, Mobile app and desktop app.
i find python quite resourceful. given the bulk of libraries that python has and the trends of the tech i find django which runs on python to be the framework of choice to the upcoming web services and application. Laravel on the other hand which is powered by PHP is also quite resourceful and great for startups and common web applications.
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 Laravel
- Clean architecture496
- Growing community357
- Composer friendly334
- Open source310
- The only framework to consider for php292
- Mvc192
- Quickly develop187
- Dependency injection154
- Application architecture141
- Embraces good community packages128
- Write less, do more56
- Restful routing49
- Orm (eloquent)45
- Artisan scaffolding and migrations42
- Database migrations & seeds42
- Awesome35
- Great documentation32
- Awsome, Powerfull, Fast and Rapid25
- Promotes elegant coding25
- Build Apps faster, easier and better24
- JSON friendly22
- Most easy for me21
- Eloquent ORM20
- Easy to learn, scalability19
- Modern PHP19
- Test-Driven19
- Blade Template18
- Beautiful18
- Security13
- Clean Documentation11
- Based on SOLID10
- Cool10
- Convention over Configuration10
- Easy to attach Middleware9
- Simple9
- Laravel + Cassandra = Killer Framework8
- Fast8
- Easy to use8
- Simpler8
- Get going quickly straight out of the box. BYOKDM8
- Easy Request Validatin8
- Simplistic , easy and faster7
- Less dependencies7
- Its just wow7
- Friendly API6
- Its beautiful to code in5
- Super easy and powerful5
- Great customer support5
- Speed4
- Fast and Clarify framework4
- The only "cons" is wrong! No static method just Facades4
- Easy4
- Active Record4
- Php74
- Laravel Mix3
- Laragon3
- Eloquent3
- Easy views handling and great ORM3
- Minimum system requirements3
- Composer3
- Intuitive usage2
- Laravel Spark2
- Laravel Passport2
- Laravel Nova2
- Laravel casher2
- Laravel Horizon and Telescope2
- Laravel Forge and Envoy2
- Ease of use2
- Cashier with Braintree and Stripe2
- Rapid development1
- Scout0
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 Laravel
- PHP38
- Too many dependency24
- Slower than the other two19
- A lot of static method calls for convenience15
- Too many include13
- Heavy10
- Bloated7
- Laravel6
- Confusing5
- Does not work well for file uploads in Shared Hosting4
- Too underrated3
- Not fast with MongoDB2
- Difficult to learn1
- Not using SOLID principles1