What is Polymer and what are its top alternatives?
Top Alternatives to Polymer
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...
It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications. ...
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
It is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness. ...
Material Design for Angular
Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs. ...
Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices. ...
It is a comprehensive guide for visual, motion, and interaction design across platforms and devices. ...
Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more. ...
Polymer alternatives & related posts
- Virtual dom646
- Data flow171
- Isn't an mvc framework122
- Reactive updates112
- Explicit app state109
- Learn once, write everywhere21
- Uni-directional data flow17
- Easy to Use16
- Works great with Flux Architecture14
- Great perfomance9
- Built by Facebook6
- Feels like the 90s4
- TypeScript support3
- Easy to start3
- Server side views3
- Fast evolving2
- Great migration pathway for older systems2
- Simple, easy to reason about and makes you productive2
- Fancy third party tools2
- Excellent Documentation2
- Scales super well2
- Just the View of MVC2
- Server Side Rendering2
- Rich ecosystem2
- Split your UI into components with one true state1
- Every decision architecture wise makes sense1
- Super easy1
- Beautiful and Neat Component Management1
- Has functional components1
- Very gentle learning curve1
- Strong Community1
- Has arrow functions1
- Allows creating single page applications1
- Start simple0
- Requires discipline to keep architecture organized31
- No predefined way to structure your app19
- Need to be familiar with lots of third party packages18
- Not enterprise friendly6
- State consistency with backend neglected1
- One-way binding only1
related React posts
I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.
I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.
It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.
- It's a powerful framework92
- Straight-forward architecture47
- Great UI and Business Logic separation39
- Powerful, maintainable, fast37
- Amazing CLI33
- Great mvc30
- Powerfull Dependency Injection22
- Easy to build17
- Opinionated, batteries-included approach12
- All in one Framework9
- Solid Standard Setup.7
- Only for single page applications3
- Large overhead in file size and initialization time7
- CLI not open to other test and linting tools2
- Ugly code1
related Angular 2 posts
When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:
- Many in our community are already using React internally and will be able to contribute.
- Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.
So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.
From my experience of the early startup world, a majority of companies these days use Node.js. Python and Go are the next biggest languages, but significantly smaller than Node.
However, if you're having trouble with the front end aspect of Django, using Node probably won't make that easier for you. You'll have a lot more options between front end frameworks (React, Vue.js, Angular 2) , but they'll definitely take more time to learn than Django's templating system.
Think about whether you want to focus on front end or back end for now, and make a decision from there.
- UI components1.2K
- Great docs776
- HTML, CSS, and JS framework466
- Open source410
- Widely used375
- HTML framework241
- Mobile first75
- Easy setup75
- Great grid system56
- Great community49
- Future compatibility38
- Very powerful foundational front-end framework27
- Build faster prototypes19
- Good for a person who hates CSS7
- Easy to setup and learn4
- Rapid development4
- Love it4
- Great and easy to make a responsive website2
- Sprzedam opla2
- Powerful grid system, Rapid development, Customization2
- Clean and quick frontend development2
- Easy to use2
- Great customer support2
- The fame1
- Easy setup21
- Painless front end development1
- So clean and simple1
- Numerous components1
- Pre-Defined components1
- Great and easy1
- It's fast1
- Great and easy to use1
- Responsive design1
- Design Agnostic1
- Provide angular wrapper1
- Love the classes?1
- Felxible, comfortable, user-friendly1
- Every site uses the defaults14
- Too much heavy decoration in default look11
- Grid system break points aren't ideal11
- Verbose styles7
related Bootstrap posts
I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.
I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).
As per my work experience and knowledge, I have chosen the followings stacks to this mission.
Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.
Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.
Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.
Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.
Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.
Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.
Happy Coding! Suggestions are welcome! :)
related Animate.css posts
- Ui components114
- Backed by google62
- Backed by angular50
- Open source34
- Easy to learn31
- Quick to develop28
- Easy to start8
- Flexbox Layouts4
- I like its design3
- Great community3
- Great extensions2
- It's the best looking out of the box1
- Seamless integration with AngularJS but lack of docs1
- Progressive Web Apps - to learn0
- No practical examples3
related Material Design for Angular posts
- Responsive grid158
- Mobile first92
- Open source79
- Quick to prototype51
- Simple ui50
- Best practices44
- Easy setup39
- Neutral style6
- HTML, SCSS and JS6
- Accessibility support5
- Xy grid3
- Every new version is smaller, smarter & more efficient2
- Requires jQuery4
- Awful site4
related Foundation posts
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
- Material Design67
- Ui components42
- CSS framework22
- Looks great10
- Open source6
- Good documentation6
- Code examples5
- Ui component4
- Very accessible3
- Designed for Server Side Rendering2
- Supports old browsers out of the box2
- Easy to work with1
- Hard to learn. Bad documentation22
- Hard to customize20
- Hard to understand Docs15
- For editable table component need to use material-table4
- Long Code4
- Bad performance4
- Extra library needed for date/time pickers4
related Material-UI posts
I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.
A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.
In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.
If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.
Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.
Here is a list of my requirements.
- Good documentation.
- easy CRUD ( date picker and date range picker bundled )
- built-in multi-lang feature or Great 3rd library support
- Admin dashboard template
- well code maintenance
Which is better for the long run?
- Automatic routes31
- Hot code reloading18
- Static Websites15
- Easy setup, easy to use, great community, FRENCH TOUCH14
- Code splitting for every page11
- Custom layouts9
- Automatic transpilation and bundling (with webpack and9
- Modules ecosystem7
- Easy setup6
- Vibrant and helpful community5
- Pages directory5
- Amazing Developer Experience4
related Nuxt.js posts
Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:
- Vue Styleguidist as our style guide and pool of developed Vue.js components
- Vuetify as Material Component Framework (for fast app development)
- TypeScript as programming language
- Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
- ESLint, TSLint and Prettier for coding style and code analyzes
- Jest as testing framework
- Google Fonts and Font Awesome for typography and icon toolkit
- NativeScript-Vue for mobile development
The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:
- Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
- Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
- Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
- Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
- Large scaling. Vue.js can help to develop pretty large reusable templates.
- Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.