.NET vs GraPHP

Overview

.NET

Stacks15.3K

Followers5.9K

Votes1.9K

GitHub Stars21.7K

Forks4.9K

GraPHP

Stacks0

Followers6

Votes0

.NET vs GraPHP: 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; GraPHP: *A PHP graph DB web framework *. The goal of this project is to build a lightweight web framework with a graph DB abstraction. It should be very easy to create the graph schema with no knowledge of of how the data is stored. Also, the schema should be incredibly flexible so you should never need migrations when adding new models (nodes), connections (edges), or data that lives in nodes.

.NET and GraPHP can be primarily classified as "Frameworks (Full Stack)" tools.

Some of the features offered by .NET are:

Multiple languages: You can write .NET apps in C#, F#, or Visual Basic.
Cross Platform: Whether you're working in C#, F#, or Visual Basic, your code will run natively on any compatible OS.
Consistent API & Libraries: To extend functionality, Microsoft and others maintain a healthy package ecosystem built on .NET Standard.

On the other hand, GraPHP provides the following key features:

Full MVC. Zero boilerplate controllers, models, and views.
Models are your schema. Defining data is up to you (but not required).
No migrations. Team members can add new models independently without conflicts

.NET and GraPHP are both open source tools. .NET with 11.1K GitHub stars and 2.4K forks on GitHub appears to be more popular than GraPHP with 135 GitHub stars and 5 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on .NET, GraPHP

Ing. Alvaro

Software Systems Engineer at Ripio

Nov 28, 2020

Decided

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!

399k views399k

Comments

Ing. Alvaro

Software Systems Engineer at Ripio

May 21, 2020

Decided

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.

524k views524k

Comments

Mohammed

Jun 27, 2021

Needs adviceon

Django

I'm working in a university in the IT department where they are developing web Apps with a .NET framework, and I'm starting a master course with python (python programming, ML, AI, NLP, and Django). My manager doesn't mind using any technology.
Please guide me. Should I go to learn .NET with Django or stick with Django? What is the best for the future?

80.4k views80.4k

Comments

Detailed Comparison

.NET	GraPHP
.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.	The goal of this project is to build a lightweight web framework with a graph DB abstraction. It should be very easy to create the graph schema with no knowledge of of how the data is stored. Also, the schema should be incredibly flexible so you should never need migrations when adding new models (nodes), connections (edges), or data that lives in nodes.
Multiple languages: You can write .NET apps in C#, F#, or Visual Basic.; Cross Platform: Whether you're working in C#, F#, or Visual Basic, your code will run natively on any compatible OS.; Consistent API & Libraries: To extend functionality, Microsoft and others maintain a healthy package ecosystem built on .NET Standard.; Application models for web, mobile, games and more: You can build many types of apps with .NET. Some are cross-platform, and some target a specific OS or .NET implementation.; Choose your tools: The Visual Studio product family provides a great .NET development experience on Windows, Linux, and macOS. Or if you prefer, there are .NET command line tools and plugins.	Full MVC. Zero boilerplate controllers, models, and views.;Models are your schema. Defining data is up to you (but not required).;No migrations. Team members can add new models independently without conflicts;No DB queries, unless you want to. Transparent model makes it easy to see what happens under the hood.;DB API is designed for fast performance. No implicit joins or other magic, but expressive enough for nice readable code.;No CLI needed (but supported for cron and tests).;All classes are loaded on demand when used for the first time.;PHP 5.5+
Statistics
GitHub Stars 21.7K	GitHub Stars -
GitHub Forks 4.9K	GitHub Forks -
Stacks 15.3K	Stacks 0
Followers 5.9K	Followers 6
Votes 1.9K	Votes 0
Pros & Cons
Pros 273 Tight integration with visual studio 262 Stable code 191 Great community 184 Reliable and strongly typed server side language. 141 Microsoft Cons 13 C# 12 Too expensive to deploy and maintain 8 Microsoft dependable systems 8 Microsoft itself 5 Hard learning curve	No community feedback yet
Integrations
C# Microsoft Azure F# Xamarin Visual Basic	PHP

What are some alternatives to .NET, GraPHP?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It 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.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Phoenix Framework

Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.

Related Comparisons

Some of the features offered by .NET are:

Multiple languages: You can write .NET apps in C#, F#, or Visual Basic.
Cross Platform: Whether you're working in C#, F#, or Visual Basic, your code will run natively on any compatible OS.
Consistent API & Libraries: To extend functionality, Microsoft and others maintain a healthy package ecosystem built on .NET Standard.

On the other hand, GraPHP provides the following key features:

Full MVC. Zero boilerplate controllers, models, and views.
Models are your schema. Defining data is up to you (but not required).
No migrations. Team members can add new models independently without conflicts

.NET and GraPHP are both open source tools. .NET with 11.1K GitHub stars and 2.4K forks on GitHub appears to be more popular than GraPHP with 135 GitHub stars and 5 GitHub forks.

.NET vs GraPHP