VueJS / ReactJS / Angularjs / Angular 2+ Show of hands

R

rawoke

Well-Known Member
Joined
Dec 2, 2009
Messages
277
Reaction score
0
HI Guys
I was wondering how the s.a web dev community is made up in terms of javascript frameworks..
Of course each has their pro's and cons but was wondering what the s.a community currently prefers ?

I was/is a strong Angularjs1 guy now leaning towards VueJs
 
Last edited:
Elm is conceptually awesome. Using it in a team to build UI is another story
 
Depends on the solution and the team. I like Vue. Angular not so much. Have a soft spot for Knockout.
 
I have used AngularJS, React, Vue and Angular (v2 & v4) in projects.

I personally prefer angular when building larger apps as it is more of a framework than the others. Vue is great and easy to use but personally don't use it as there is no fully featured 'native' library (yet) like those for react/angular (some might see this as a non issue).

React is great and easy to use however I just don't like JSX and with react you will need to use other libraries e.g. flux/redux for state and other framework stuff as react is not a full framework. React is just one piece of the puzzle for a modern fully featured web app where you can get away with only using angular as it is a full framework. There is also more free rain in react and projects will look different(which is not wrong, I just dont like it). Dont get me wrong people can really screw up an angular project but at least if you stick to the cli most projects will be sort of the same.

AngularJS is nice and even though I think the angular team should have given angular 2+ a new name completely (aka new framework instead of v2), I really like angular and the new direction. I think out of the ones mentioned above the the tooling for Angular is superior to the others except that reactnative might be > nativescript (but that is debatable).

For new projects I will go angular and probably try out elm in the future.

But like kripstoe said, it all depends on the project what you should use. Or you can just do what one of my previous bosses did and create a custom framework built on JQuery for every new project without any standards or documentation.
 
I have used Angular 2 just when it came out and again recently.
First time around it was terrible, near no documentation at the time, more recently it was all right. It's becoming quite nice to work with, especially using WebStorm (the difference between WebStorm and Visual Code is like night and day, quite happy that they allow students to use it for free).
 
Doesn't matter, any of the above, with a preference for small/micro frameworks. Or, when the mood takes me I'll write my own lib built for purpose. React/Vue/Angular will come and go... It's the ideas/understanding that matters.
 
I use some knockout, but that is mainly maintenance of old projects. All our new projects are using react, and there may be a couple of rewrites of knockout code to react.
 
More importantly, what do you guys want from a framework/toolkit. Templating, data/event binding, State/History management, which features of your chosen libs/frameworks do you like the most? Me, personally, pubsub for events, streams for data and promises/fp to chew through everything in between.
 
John_Phoenix said:
More importantly, what do you guys want from a framework/toolkit. Templating, data/event binding, State/History management, which features of your chosen libs/frameworks do you like the most? Me, personally, pubsub for events, streams for data and promises/fp to chew through everything in between.
Click to expand...

Ease of use. Data/event binding. Maintainability.

But again. Depends on the use case. And the team.
 
Ja i'm starting to use VueJS more and more. I'm very impressed with it ! Like the VUE file thing... vue-cli !
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X