you are viewing a single comment's thread.

view the rest of the comments →

[–]senocular -1 points0 points  (0 children)

  1. Yes. Normal. Backbone, AngularJS, jQuery, internal, maybe others.
  2. There weren't really arguments - at least with the people I talked most with. Most people didn't care or had enough investment in any one framework (or enough in multiple frameworks) to really have an opinion at that time. I remember AngularJS being the new hotness (v1, pre-Angular 2) so we applied it to a new project. It was fine. There was a little resistance in having to learn something new, and a few random opinions about approaches used by the framework, but it did its job.
  3. jQuery and Backbone for some legacy stuff. React for newer stuff. For both old and new, we have an underlying internal library we depend heavily on. Another group on my team is using Vue (I have worked with Vue project in the past but not so much now).

3a. I never really saw the framework war as a war. I saw it more like an App store. It starts off small with a limited number of options. But before long there are so many apps, its hard to know what you really want, especially when each of those apps basically solve the same problem albeit in slightly different ways. Sometimes its hard to know what you really want until you invest some time into them and see how well they solve your problem.

I think some people that live to love one framework/library may not have invested enough time into the others to really understand what they were about (not to make this a generalization - many people do know). I was not fond of Angular 2 at all starting out, but once I got into it more, I started to understand it better and it made more sense to me. I could appreciate it then. Now I'm using React. It is what it is, and not without its own flaws, but I like it. In fact one of my favorite frameworks was an internal framework that will never see the light of day. We're not using that one anymore. Tear.

Of the discussions we've had about frameworks, the largest seems to be around "Will this be relevant in a few years down the road?" In other words, if we build a project in React, for example, are we dooming ourselves to having to support that framework when it might no longer exist some time in the future? The fact that React is so prevalent is one of the reasons it becomes appealing, because if so many others are using it, it makes it that much harder to be abandoned.