Buffalo vs .NET Core: What are the differences?
Developers describe Buffalo as "MVC Web Framework for Go". Buffalo is Go web framework. Yeah, I hate the word "framework" too! Buffalo is different though. Buffalo doesn't want to re-invent wheels like routing and templating. Buffalo is glue that wraps all of the best packages available and makes them all play nicely together. On the other hand, .NET Core is detailed as "An Open Source, General-Purpose Development Platform Maintained by Microsoft and the .NET Community". Cross-platform (supporting Windows, macOS, and Linux) and can be used to build device, cloud, and IoT applications.
Buffalo and .NET Core can be categorized as "Frameworks (Full Stack)" tools.
"Go" is the primary reason why developers consider Buffalo over the competitors, whereas "Great performance" was stated as the key factor in picking .NET Core.
Buffalo and .NET Core are both open source tools. It seems that .NET Core with 11.2K GitHub stars and 2.41K forks on GitHub has more adoption than Buffalo with 4.64K GitHub stars and 362 GitHub forks.