3 ms·
Which technology stack would you recommend going forward? And why? Node.js? Vue.js? React? Angular? Elm? I can't keep up with the Javascript tower of bab
by blackrock 8y ago
Which technology stack would you recommend going forward? And why?
Node.js? Vue.js? React? Angular? Elm?
I can't keep up with the Javascript tower of babel anymore.
And what happened to Django? Nobody seems to talk about it anymore.
- iamcasen 8y agoDjango is by far the best full-stack MVC solution IMO. It is well known in python communities, and python is growing in popularity year over year. As for your javascript questions: React is the answer. Not just because it has the considerable resources of Facebook backing it, but because at it's core, the idea is extremely sound and well tested, going back 30 or more years. Vue.js has similar principles and might also be a good choice, but what you need to look out for is the community surrounding it, and whether it will eventually be unsupported. Node.js is great in the backend, but doesn't have quite as many mature frameworks like Django. If you're down to build things from bare metal using some libraries like Express.js or Koa.js, then you'll enjoy Node.js. Typescript and Flow have also made Node more attractive.
- deltron3030 8y ago> Which technology stack would you recommend going forward? And why? With React you have the most options and biggest community, including ways to shoot yourself in the foot. It's preferred by full stack JS guys who also use node, so it could be great if you're a startup and can hire somebody who can do everything. Angular is popular with enterprises who know what they need (a stable environment at scale with strict rules), who have a high budget for hiring specialists, the whole framework is more complex. Vue sits in between Angular and React, but more geared towards smaller businesses and their needs. It's very popular with PHP devs, and full stack devs who don't use JS exclusively. The main advantage is peace of mind, knowing that everything works well togehter. Elm is very opinionated, but also very different from those other frameworks. In React or Vue you start thinking of components, in Elm you think about functionality, and create components as they emerge from patterns, potentially leading to a more cohesive and elegant result. But that's not how designers used to work. Bridging the gap between designers and devs, and how they currently work, is the main advantage of React and Vue imo. Web designers (like graphic designers) are used to think in whole pages, or layouts, and break things down from there (top-down). React and Vue and the component first paradigm is a compromise, where devs aren't degraded into only doing the implemetation, and designers aren't degraded into doing the styling only. It still respects both roles. Elm is basically the next level for designers, or designers who like to code. It's how design that left the analog world behind could be.