Application and Data / Languages & Frameworks / Javascript MVC Frameworks
Avatar of jakestein
CEO at Stitch

Stitch鈥檚 frontend is used to configure data sources and destinations and monitor the status of each. Although we have been using AngularJS since its early days, we recently introduced React components into our front end, which many of our developers find easier to work with. We started using CoffeeScript when it was one of the few options for a more expressive alternative to vanilla JavaScript, but today we opt to instead write new code in ES6, which we feel is a more mature alternative.

How Stitch Consolidates A Billion Records Per Day - Stitch Tech Stack | StackShare (
15 upvotes2 comments121.9K views

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.

React migration 路 Issue #3071 路 getredash/redash 路 GitHub (
14 upvotes141.1K views

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.

12 upvotes3 comments69.2K views
Avatar of rafaelspecta
CTO at Decision6

Back in 2015, my company had a back-office dashboard that was originally built in AngularJS 1. Since Angular 2 presented drastic changes we decided to rethink the options and we looked at React and Vue.js. Besides, at the time, Vue had basically only one developer, its structure (100% oriented to components) and also its backward compatibility focus (Angular 1 to 2 no more) we preferred it against React cause it seemed more straightforward, clean and with a small learning curve. Now 4-5 years later we are very happy with our choice.

11 upvotes19.2K views

We had contemplated a long time which #JavascriptMvcFrameworks to use, React and React Native vs AngularJS and Apache Cordova in both web and mobile. Eventually we chose react over angular since it was quicker to learn, less code for simple apps and quicker integration of third party javascript modules. for the full MVC we added Redux.js for state management and redux-saga for async calls and logic. since we also have mobile app along with the web, we can shere logic and model between web and mobile.

10 upvotes112.2K views
Avatar of bananatron
Product Engineer at

When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

8 upvotes191K views
Avatar of across_the_grid
Full-stack web developer at Capmo GmbH
Shared insights

I use AngularJS because it was back in the days one of the interesting and most hyped frameworks. Especially the two-way databinding and the amount of free angular-components from the community made the development of this research project very easy and fast. React on the other side, was just on the geginning of its rise and Angular promised a more SPA approach, also with HTML & CSS templating, which I had experience from the past. React with JSX was too new for me and a bigger overhead, so I tried AngularJS. Today with no backward support of Angular 2.x/ - /8.x, I personally switched to Vue.js as it shares many concepts from Angular & React and is easy to learn.

5 upvotes1 comment7K views
Avatar of adamrabinovitch
Global Technical Recruiting Lead & Engineering Evangelist at Beamery

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.

Using Micro-Frontends to Permanently Solve the Legacy JavaScript Problem (
4 upvotes54.7K views
Needs advice

I am very comfortable in Django. For the front-end I love AngularJS. I want to know whether it's okay to stick with Django or should I go for Node.js.

4 upvotes411 views
Replies (5)
Avatar of michaelmota
CEO & Founder at AlterEstate

I've been using Django for quite a long time and in my opinion I would never switch from it. My company is currently using Django with REST framework and a part in GraphQL using Graphene. On the frontend we use Next.js and so far everything has been running quite good. I've found limitations but manage to solve it.

As someone mentioned before, if you are comfortable with Django, don't switch. There's no need since with django you can basically achieve anything. Of course this will depend on the project you want to build, but the scalability and flexibility django can offer it's just out of this world. (Don't want to sound like a fan boy haha but it really is).

4 upvotes2.1K views
Avatar of danielrvt
Director at Drag & Drop Solutions

It's been ages since I last used Django, but if you're proficient with it, I'd suggest you stick to it in order to deliver results quickly and on time. On the other hand, if time is not an issue, I'd recommend you start learning Node.js with express.js or loopback.js.

I haven't found something similar to Django in terms of a built in full fledge admin and CMS but, in my opinion, since you are using JavaScript (Angular.js) on the frontend, I think you could benefit from using JavaScript in the backend.

Bottom line: Start learning Node, keep using Django till you get proficient at Node, then move to Node ;)

I haven't found anything close to the Django admin in Node.

Keep in mind that comparing Node.js with Django is not quite right. It's like comparing Python with express.js

3 upvotes1 view
View all (5)

Both are very good! But I started with Visual Studio Code when I started to work with AngularJS 4. I tried to use Atom too, but at that time Atom did not have good Angular plugins, in the other side VS Code has nice plugins for Angular. I do not know how is Atom now a days about this, but I think that it must have evolved.

3 upvotes7.9K views