AngularJS vs. Laravel

  • 922
  • 1.02K
  • 258K
  • 516
  • 3.75K
  • 112K

What is 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鈥檚 syntax to express your application鈥檚 components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

What is Laravel?

Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel 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.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose AngularJS?
Why do you like AngularJS?

Why do developers choose Laravel?
Why do you like Laravel?

What are the cons of using AngularJS?
Downsides of AngularJS?

What are the cons of using Laravel?
Downsides of Laravel?

What companies use AngularJS?
3509 companies on StackShare use AngularJS
What companies use Laravel?
1036 companies on StackShare use Laravel
What tools integrate with AngularJS?
30 tools on StackShare integrate with AngularJS
What tools integrate with Laravel?
17 tools on StackShare integrate with Laravel

What are some alternatives to AngularJS and Laravel?

  • React - A JavaScript library for building user interfaces
  • jQuery - The Write Less, Do More, JavaScript Library.
  • Vue.js - Reactive Components for Modern Web Interfaces
  • jQuery UI - Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library

See all alternatives to AngularJS

What鈥檚 new in Angular 5
Custom error handling for Angular
6 common misconceptions about Angular
Laravel Vouchers
Laravel Postal Code Validation
Tailwind 1.0.0 Beta Release
Related Stack Decisions
Arik Fraimovich
Arik Fraimovich
Vue.js
React
Angular 2
AngularJS

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
Adam Rabinovitch
Adam Rabinovitch
Senior Technical Recruiter & Engineering Evangelist at Beamery | 3 upvotes 4994 views
atBeamery
Polymer
Aurelia
Vue.js
Angular 2
React
AngularJS
#Hiring

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鈥檛 scale nicely. Features clash with each other. Isolation doesn鈥檛 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
Gianluca Bargelli
Gianluca Bargelli
MobX
Redux.js
AngularJS
React

We started rebuilding our dashboard components using React from AngularJS over 3 years ago and, in order to have predictable client-side state management we introduced Redux.js inside our stack because of the popularity it gained inside the JavaScript community; that said, the number of lines of codes needed to implement even the simplest form was unnecessarily high, from a simple form to a more complex component like our team management page.

By switching our state management to MobX we removed approximately 40% of our boilerplate code and simplified our front-end development flow, which in the ends allowed us to focus more into product features rather than architectural choices.

See more


Interest Over Time