Need advice about which tool to choose?Ask the StackShare community!
ASP.NET vs Processing: What are the differences?
What is ASP.NET? An open source web framework for building modern web apps and services with .NET. .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
What is Processing? A programming language for people who want to program images, animation, and interactions for the web. It is an open programming language for people who want to program images, animation, and interactions for the web without using Flash or Java applets.
ASP.NET belongs to "Frameworks (Full Stack)" category of the tech stack, while Processing can be primarily classified under "Languages".
Processing is an open source tool with 2.9K GitHub stars and 787 GitHub forks. Here's a link to Processing's open source repository on GitHub.
According to the StackShare community, ASP.NET has a broader approval, being mentioned in 12570 company stacks & 334 developers stacks; compared to Processing, which is listed in 13 company stacks and 7 developer stacks.
When I started on this project as the sole developer, I was new to web development and I was looking at all of the web frameworks available for the job. I had some experience with Ruby on Rails and I had looked into .net for a bit, but when I found Laravel, it felt like the best framework for me to get the product to market. What made me choose Laravel was the easy to read documentation and active community. Rails had great documentation, but lacked some features built in that I wanted out of the box, while .net had a ton of video documentation tutorials, but nothing as straightforward as Laravels. So far, I am happy with the decision I made, and looking forward to the website release!
Comparing to ASP.NET Core MVC or ASP.NET Core Web API Simplify.Web allows you to easily build your web-site or REST API without any additional/complicated setup, covering cases like localization by default. It's projects structure very lightweight, just a minimum amount of what you need to setup ASP.NET Core request pipeline.
It is build on top of Simplify.DI IOC container abstraction, no dependency on Microsoft.Extensions.DependencyInjection and it's syntax. You can easily switch between DryIoc, SimpleInjector, CastleWindsor etc.
Any internal module of Simplify.Web can be easily replaced on extended by your custom module, covering your custom cases.
For HTML pages generation Simplify.Templates can be used allowing you to use just regular plain HTML without additional setup.
Can be easily integrated with Simplify.WindowsServices converting your web application not just to web-application, but a standalone windows service which can also do some background jobs via Simplify.WindowsServices.
And it is open source, of course :)
Pros of ASP.NET
- Great mvc21
- Easy to learn13
- C#6
Pros of Processing
Sign up to add or upvote prosMake informed product decisions
Cons of ASP.NET
- Entity framework is very slow2
- C#1
- Not highly flexible for advance Developers1
Cons of Processing
Sign up to add or upvote consMake informed product decisions
What is ASP.NET?
What is Processing?
Need advice about which tool to choose?Ask the StackShare community!
What companies use ASP.NET?
What companies use Processing?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Processing?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+12