Need advice about which tool to choose?Ask the StackShare community!
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 Dancer
- Fast1
- Easy1
- Stable1
- Microframework1
Pros of .NET
- Tight integration with visual studio271
- Stable code261
- Great community189
- Reliable and strongly typed server side language.182
- Microsoft140
- Fantastic documentation119
- Great 3rd party libraries89
- Speedy80
- Great azure integration71
- Great support63
- Highly productive34
- C#34
- Linq34
- High Performance31
- Great programming languages (C#, VB)28
- Open source25
- Powerful Web application framework (ASP.NET MVC)19
- Clean markup with razor16
- Fast16
- Powerful ORM (EntityFramework)15
- Dependency injection13
- Constantly improving to keep up with new trends10
- Visual studio + Resharper = <310
- High-Performance9
- Security8
- TFS8
- Huge ecosystem and communities7
- Integrated and Reliable7
- Job opportunities7
- Light-weight6
- Lovely6
- Asynchrony5
- Variations5
- {get; set;}5
- Concurrent4
- Support and SImplicity4
- Default Debuging tools4
- Useful IoC4
- Scaffolding4
- Entity framework4
- Blazor3
- F♯2
- Nuget package manager2
Pros of Mojolicious
- Perl is still awesome18
- Open source17
- Real-time16
- True async14
- WebSockets12
- Lightweight9
- Super easy, fast, and elegant application development9
- Well designed7
- Amazing and fun to use6
- Cons0
Sign up to add or upvote prosMake informed product decisions
Cons of Dancer
Cons of .NET
- C#13
- Too expensive to deploy and maintain12
- Microsoft dependable systems8
- Microsoft itself8
- Hard learning curve5
- Tight integration with visual studio3
- Not have a full fledged visual studio for linux3
- Microsoft itself 🤡🥲1
Cons of Mojolicious
Sign up to add or upvote consMake informed product decisions
What is Dancer?
What is .NET?
What is Mojolicious?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Dancer?
What companies use .NET?
What companies use Mojolicious?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Dancer?
What tools integrate with .NET?
What tools integrate with Mojolicious?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+3
+12
+22+27