StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. .NET vs Polymer

.NET vs Polymer

OverviewDecisionsComparisonAlternatives

Overview

.NET
.NET
Stacks15.4K
Followers5.9K
Votes1.9K
GitHub Stars21.7K
Forks4.9K
Polymer
Polymer
Stacks557
Followers463
Votes122
GitHub Stars22.1K
Forks2.0K

.NET vs Polymer: What are the differences?

Introduction: In web development, developers often have to choose between different frameworks like .NET and Polymer to build their applications. Understanding the key differences between the two can be crucial in deciding which one suits the project requirements the best.

1. Architecture Approach: .NET is a framework developed by Microsoft that follows the server-side architecture approach, where most of the processing happens on the server. On the other hand, Polymer is a front-end library that focuses on client-side processing, leveraging the power of the user's browser.

2. Language Compatibility: .NET primarily supports languages like C# and VB.NET, which are statically typed, while Polymer is primarily based on JavaScript, a dynamically typed language. This difference in language compatibility can influence the choice of framework based on the developer's preference and expertise in a particular language.

3. Component-Based Development: Polymer is known for its strong emphasis on component-based development, allowing developers to create reusable elements that can be easily integrated into various parts of the application. .NET, on the other hand, does support component-based development but may not have the same level of flexibility and ease of use as Polymer.

4. Ecosystem and Community Support: .NET has a strong ecosystem backed by Microsoft, providing a wide range of tools, libraries, and support for developers. In comparison, Polymer is more community-driven, with a focus on open-source contributions and collaborations. The choice between the two frameworks can depend on the level of support and resources needed for the project.

5. Performance and Scalability: When it comes to performance and scalability, .NET is known for its robustness and efficiency in handling large-scale applications with high traffic. Polymer, on the other hand, may face limitations in terms of performance optimization, especially when dealing with complex applications that require streamlined processing.

6. Tooling and Integration: .NET offers a comprehensive suite of integrated development tools, such as Visual Studio, that provide a seamless development experience for developers. On the other hand, Polymer may require additional setup and integration with tools like Webpack or Babel to achieve a similar level of productivity and efficiency. This difference in tooling can impact the development process and the overall project timeline.

In Summary, understanding the key differences between .NET and Polymer, such as architecture approach, language compatibility, component-based development, ecosystem support, performance, and tooling, is essential in making an informed decision when choosing a framework for web development projects.

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)
or
Manual

Advice on .NET, Polymer

Ing. Alvaro
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
Gericke
Gericke

Jul 27, 2020

Needs adviceon.NET Core.NET CoreJavaScriptJavaScriptReactReact

Hi,

I am looking into solutions for reusable components for an existing #MVC project which is build on .NET Core. Currently some functionality is being reuses via JavaScript. I have React experience so I know I can create React components and then reference it on the MVC app. The only problem is I do not know the full extent of it as the current app uses a lot of 3rd party libraries, not sure how that will effect React components. I am currently looking into WebComponents which is also another way for creating reusable components and it is compatible with any JavaScript library based on what I have seen on the website. Also to take in consideration that it should cause a re-write of the system.

So my question is, to future-proof reusable components, which will be best React or Web Components? And which will be more reliable to use with 3rd party libraries?

49.2k views49.2k
Comments

Detailed Comparison

.NET
.NET
Polymer
Polymer

.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.

Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds.

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.
-
Statistics
GitHub Stars
21.7K
GitHub Stars
22.1K
GitHub Forks
4.9K
GitHub Forks
2.0K
Stacks
15.4K
Stacks
557
Followers
5.9K
Followers
463
Votes
1.9K
Votes
122
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
Pros
  • 52
    Web components
  • 30
    Material design
  • 14
    HTML
  • 13
    Components
  • 5
    Open source
Cons
  • 1
    Last version is like 2 years ago? that's totally rad
Integrations
C#
C#
Microsoft Azure
Microsoft Azure
F#
F#
Xamarin
Xamarin
Visual Basic
Visual Basic
No integrations available

What are some alternatives to .NET, Polymer?

Node.js

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.

Bootstrap

Bootstrap

Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.

Rails

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

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

Laravel

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

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

Symfony

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

Spring

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

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 SDK

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

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase