Alternatives to Ampersand.js logo

Alternatives to Ampersand.js

AngularJS, Vue.js, Backbone.js, Angular 2, and Ember.js are the most popular alternatives and competitors to Ampersand.js.
16
21
+ 1
31

What is Ampersand.js and what are its top alternatives?

We <3 Backbone.js at &yet. It’s brilliantly simple and solves many common problems in developing clientside applications. But we missed the focused simplicity of tiny modules in node-land. We wanted something similar in style and philosophy, but that fully embraced tiny modules, npm, and browserify. Ampersand.js is a well-defined approach to combining (get it?) a series of intentionally tiny modules.
Ampersand.js is a tool in the Javascript MVC Frameworks category of a tech stack.
Ampersand.js is an open source tool with 819 GitHub stars and 50 GitHub forks. Here’s a link to Ampersand.js's open source repository on GitHub

Top Alternatives to Ampersand.js

  • AngularJS

    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Vue.js

    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • Backbone.js

    Backbone.js

    Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface. ...

  • Angular 2

    Angular 2

    It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications. ...

  • Ember.js

    Ember.js

    A JavaScript framework that does all of the heavy lifting that you'd normally have to do by hand. There are tasks that are common to every web app; It does those things for you, so you can focus on building killer features and UI. ...

  • Aurelia

    Aurelia

    Aurelia is a next generation JavaScript client framework that leverages simple conventions to empower your creativity. ...

  • Marionette

    Marionette

    It is a JavaScript library with a RESTful JSON interface and is based on the Model–view–presenter application design paradigm. Backbone is known for being lightweight, as its only hard dependency is on one JavaScript library, Underscore.js, plus jQuery for use of the full library. ...

  • JSF

    JSF

    It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community ...

Ampersand.js alternatives & related posts

AngularJS logo

AngularJS

39.1K
27K
5.2K
Superheroic JavaScript MVW Framework
39.1K
27K
+ 1
5.2K
PROS OF ANGULARJS
  • 885
    Quick to develop
  • 589
    Great mvc
  • 571
    Powerful
  • 522
    Restful
  • 504
    Backed by google
  • 350
    Two-way data binding
  • 344
    Javascript
  • 329
    Open source
  • 306
    Dependency injection
  • 197
    Readable
  • 75
    Fast
  • 64
    Directives
  • 63
    Great community
  • 55
    Free
  • 38
    Extend html vocabulary
  • 29
    Components
  • 25
    Easy to test
  • 24
    Easy to learn
  • 23
    Easy to templates
  • 23
    Great documentation
  • 21
    Easy to start
  • 17
    Awesome
  • 17
    Light weight
  • 14
    Angular 2.0
  • 14
    Javascript mvw framework
  • 13
    Great extensions
  • 13
    Efficient
  • 10
    Easy to prototype with
  • 8
    High performance
  • 8
    Lots of community modules
  • 8
    Coffeescript
  • 7
    Two-way binding
  • 7
    Mvc
  • 6
    Easy to e2e
  • 6
    Clean and keeps code readable
  • 5
    One of the best frameworks
  • 5
    Easy for small applications
  • 4
    Works great with jquery
  • 4
    Fast development
  • 2
    Hierarchical Data Structure
  • 2
    The two-way Data Binding is awesome
  • 2
    Community
  • 2
    Typescript
  • 2
    Declarative programming
  • 2
    I do not touch DOM
  • 2
    Be a developer, not a plumber.
  • 2
    Dart
  • 1
    Fkin awesome
  • 1
    Scopes
  • 1
    The powerful of binding, routing and controlling routes
  • 1
    Supports api , easy development
  • 1
    Opinionated in the right areas
  • 1
    Amazing community support
  • 1
    Common Place
  • 1
    Very very useful and fast framework for development.
  • 1
    Great
  • 1
    Programming fun again
  • 1
    Readable code
  • 1
    Linear learning curve
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 1.5M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 19 upvotes · 478.6K views

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
  • 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.
See more
Vue.js logo

Vue.js

30.1K
22.7K
1.3K
A progressive framework for building user interfaces
30.1K
22.7K
+ 1
1.3K
PROS OF VUE.JS
  • 258
    Simple and easy to start with
  • 204
    Good documentation
  • 176
    Components
  • 116
    Simple the best
  • 95
    Simplified AngularJS
  • 75
    Reactive
  • 65
    Intuitive APIs
  • 47
    Javascript
  • 41
    Changed my front end coding life
  • 36
    Configuration is smooth
  • 25
    Easy to learn
  • 20
    So much fun to use
  • 18
    Progressive
  • 16
    Virtual dom
  • 11
    Faster than bulldogs on hot tarmac
  • 8
    Best of Both Worlds
  • 8
    It's magic
  • 7
    Without misleading licenses
  • 7
    Application structure
  • 7
    Component is template, javascript and style in one
  • 7
    Elegant design
  • 7
    Perfomance
  • 6
    Intuitive and easy to use
  • 5
    Light Weight
  • 4
    Easy to integrate to HTML by inline-templates
  • 4
    Good command line interface
  • 3
    Like Angular only quicker to get started with
  • 3
    Small learning curve
  • 2
    Concise error messages
  • 2
    Logicless templates
  • 2
    Supports several template languages
  • 2
    High performance
  • 2
    Customer Render ending eg to HTML
  • 2
    One-way data flow
  • 2
    Single file components
  • 2
    Intuitive
  • 2
    Lots of documentation
  • 2
    Bridge from Web Development to JS Development
  • 2
    Component based
  • 1
    GUI
CONS OF VUE.JS
  • 4
    Less Common Place
  • 2
    YXMLvsHTML Markup
  • 1
    Don't support fragments
  • 1
    Only support programatically multiple root nodes

related Vue.js posts

Johnny Bell
Software Engineer at Weedmaps · | 26 upvotes · 280.6K views
Shared insights
on
Vue.jsVue.jsReactReact

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.

See more
Shared insights
on
Vue.jsVue.jsReactReact

I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

See more
Backbone.js logo

Backbone.js

5.9K
2.1K
678
Give your JS App some Backbone with Models, Views, Collections, and Events
5.9K
2.1K
+ 1
678
PROS OF BACKBONE.JS
  • 136
    Javascript structure
  • 102
    Models
  • 98
    Simple
  • 77
    Restful
  • 59
    Easy api
  • 46
    Flexible
  • 45
    Open source
  • 44
    Fast to pick up
  • 34
    Events
  • 25
    JSON
  • 8
    OOP
  • 2
    Lightweight
  • 1
    Easy customizable
  • 1
    Collections
CONS OF BACKBONE.JS
  • 1
    Requires underscore.js

related Backbone.js posts

Dan Robinson

The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

#JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

See more
Marcos Iglesias
Sr. Software Engineer at Eventbrite · | 13 upvotes · 138.3K views

We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.

But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.

With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.

See more
Angular 2 logo

Angular 2

4.2K
3.3K
406
A platform for building mobile and desktop web applications
4.2K
3.3K
+ 1
406
PROS OF ANGULAR 2
  • 91
    It's a powerful framework
  • 47
    Straight-forward architecture
  • 39
    Great UI and Business Logic separation
  • 37
    Powerful, maintainable, fast
  • 37
    TypeScript
  • 33
    Amazing CLI
  • 30
    Great mvc
  • 22
    Powerfull Dependency Injection
  • 17
    Easy to build
  • 12
    Opinionated, batteries-included approach
  • 9
    All in one Framework
  • 7
    Solid Standard Setup.
  • 7
    Schematics
  • 6
    Structured
  • 5
    Performance
  • 3
    Only for single page applications
  • 3
    Complex
  • 1
    Builders
  • 0
    React
CONS OF ANGULAR 2
  • 7
    Large overhead in file size and initialization time
  • 6
    Overcomplicated
  • 2
    CLI not open to other test and linting tools
  • 1
    Ugly code

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:

  1. Many in our community are already using React internally and will be able to contribute.
  2. 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.

See more
Max Musing
Founder & CEO at BaseDash · | 9 upvotes · 160.3K views

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.

See more
Ember.js logo

Ember.js

1.1K
741
765
A JavaScript framework for creating ambitious web apps
1.1K
741
+ 1
765
PROS OF EMBER.JS
  • 124
    Elegant
  • 96
    Quick to develop
  • 82
    Great community
  • 81
    Great mvc
  • 72
    Great router
  • 51
    Values conventions, there is one-true way to organize
  • 49
    Open source
  • 44
    Components
  • 34
    Mvc framework
  • 28
    Handlebars.js
  • 13
    Htmlbars
  • 11
    Yehuda katz
  • 10
    Tom dale
  • 10
    Great logo
  • 5
    manages large data sets on the front end easily
  • 5
    Glimmer: react-like rendering engine
  • 5
    Convention over Configuration
  • 5
    It's NOT Google or Facebook
  • 4
    Enterprise
  • 4
    Fast
  • 4
    Intelligent
  • 4
    It rocks
  • 4
    Organized
  • 3
    IE8 support
  • 3
    Fastest spinning circles
  • 3
    Good docs
  • 2
    Documentation is finally active and updated
  • 2
    Easy and Quick to develop
  • 1
    Growing community
  • 1
    Flexibility
  • 1
    For building ambitious Web apps
  • 1
    Dependency Injection
  • 1
    Comprehensive
  • 1
    Business wins
  • 1
    Great for big apps/many devs because its organized
CONS OF EMBER.JS
  • 2
    Very little flexibility
  • 2
    Too much convention, too little configuration
  • 1
    Hard to integrate with Non Ruby apps
  • 1
    Hard to use if your API isn't RESTful

related Ember.js posts

Dmitry Mukhin

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

See more

Choosing a framework be it angular, react, ember or vue is personal preference. I would say start with each and build something that utilise state management (todo list perhaps?) and see which style you are comfortable with.

If you wants to get employed, React is a wiser choice. It also helps you build native mobile apps with react-native . If you are building enterprise app with alot of client-side data, nothing beats Ember.js ember-data.

If you are like me who is prototyping light-weight startup and would like to move fast and missing your first front-end learning (angular 1), go with Vue.js . NativeScript-Vue is the binding to build mobile native apps with it.

See more
Aurelia logo

Aurelia

251
252
372
Next gen JS framework written with ES6 and ES7. Integrates with Web Components. No external dependencies except polyfills.
251
252
+ 1
372
PROS OF AURELIA
  • 47
    Simple with conventions
  • 42
    Modern architecture
  • 39
    Makes sense and is mostly javascript not framework
  • 31
    Extensible
  • 28
    Integrates well with other components
  • 27
    Easy to use
  • 25
    Dependency Injection
  • 22
    Modular
  • 20
    Great router
  • 16
    Adaptive Data Binding
  • 13
    Typescript, ES2015, ES2016
  • 11
    IoC, Modularity, Simplicity, Full Stack
  • 9
    Good binding system
  • 9
    Based on ES7
  • 6
    Testable
  • 6
    Convention based
  • 5
    Quick to develop
  • 4
    Solid Documentation
  • 4
    Evolving standards compliance
  • 4
    Smooth learning curve
  • 4
    Outstanding Support (paid)
CONS OF AURELIA
  • 4
    None

related Aurelia posts

Adam Rabinovitch
Global Technical Recruiting Lead & Engineering Evangelist at Beamery · | 5 upvotes · 108.6K views

At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn’t scale nicely. Features clash with each other. Isolation doesn’t come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

See more
Marionette logo

Marionette

154
112
79
Backbone application code with robust views and architecture solutions
154
112
+ 1
79
PROS OF MARIONETTE
  • 20
    MVC compliant
  • 20
    Uses Backbone
  • 13
    Views management
  • 9
    View management
  • 6
    JavaScript
  • 6
    Memory management
  • 4
    MVC Beginner-Friendly
  • 1
    Collections useful tools
CONS OF MARIONETTE
    Be the first to leave a con

    related Marionette posts

    Dan Robinson

    The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

    Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

    #JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

    See more
    Marcos Iglesias
    Sr. Software Engineer at Eventbrite · | 13 upvotes · 138.3K views

    We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.

    But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.

    With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.

    See more
    JSF logo

    JSF

    102
    121
    3
    It is used for building component-based web interfaces
    102
    121
    + 1
    3
    PROS OF JSF
    • 1
      Rich and comprehensive Request Life-cycle
    • 1
      Very Mature UI framework
    • 1
      Server Side component
    CONS OF JSF
      Be the first to leave a con

      related JSF posts