Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What features/modules does Vue.js lack that Angular 2/4 has? I'm considering investing in learning Vue.js and possibly using it on my next project. I've seen a lot about the features it has, but I need to know what I would be losing before I can make the leap so I can figure out if I can live without it or if there are complementary frameworks/libraries that can fill the gap.
Edit
To those voting to close this question as "Too broad", I'm not asking for a complete list of differences, just the features like routing, injection, transclusion, etc.
AngularJS has strong opinions on how an application should be structured i.e. routing e.t.c. Vue's sole purpose is to be a framework on the View layer.
The Vue community has contributed to solving the other common problems around developing SPAs i.e.
For routing: vue-router
For state management: vuex
For HTTP requests: axios, vue-resource e.t.c
For futher reading:
Comparison between Vue.js and Angular1
A curated list of awesome things related to Vue.js
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Can I use multiple frameworks on a single website page?
I try to use multiple frameworks like Angular, Vue, or React in one website view .. is that good or we can only use one
Yes. It is usually done in big enterprise setting with many separate front-end teams each responsible for a smaller portion of a single web app. Architecting a clean approach for it can be difficult so I recommend that you avoid it if you can. Problems include:
How to handle routing such that intra- and inter-framework routes work.
How to share state (such as auth tokens) between apps.
How to share components (and code in general) between apps.
How to avoid importing the same library used by separate frameworks twice.
A popular approach is called micro frontends which mimics the micro service approach for the front end. I’m not aware of any research for how well this works in the wild.
An example (meta) framework that handles this kind of architecture for you is single-spa.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Welcome stackoverflow community.
I'm doing small project, simple single-page website. It will also contain contact form which takes user to different page. I decided to create a database since on website I will do few responsive features ie. booking calendar where occupied dates won't be available. I wrote all my projects in vanilla js so far. I'm wondering that adding react to this project will be overkill.
I did research and know roughly cons and props for using it but I couldn't find answer if react gives you some extra safety features comparing to using vanilla js over attacks to website, and if yes, does it makes sense to write whole project in react just for those features?
Many thanks for any feedback.
I don't think you should be rewriting your app in react just for security. If you have any sensitive information. You should be keeping it on the server and not on the front-end.
For a small project. Vanilla JS can be enough. React is just for helping you manage and create UI components. It will not give you any extra security as it is still javascript in the end.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I've been coding React for the last couple of months now. I thought, initially, just going through the React official docs would be sufficient. But I've had to learn some other tools in order to really make my apps useful/easier to developer. For example, tools like Redux and react-router. How come these tools don't already come with React officially? What's the true purpose of React vs other JS frameworks?
ReactJs is not a framework ,it's a JavaScript library and it's not a language ,it's build upon JavaScript . It's a way to solve your common problems and complex tasks easy to do.
Angularjs/Angular is a fully fledged framework - it gives you built-in solutions for promises ($q), ajax calls ($http), routing and intra-component communication via services amongst others.
Reactjs on the other hand is much less opinionated. It provides a mechanism to layout and structure view code and practically nothing else (from the list above). So it's much lighter weight and you are much freer to use other libraries/packages where you feel it is necessary.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am not asking "what are differences between Ember and Backbone." It's been asked before, and doesn't answer my question.
I don't need to consider syntax, or origin stories, or my developers' coding backgrounds, community size, or which is more lightweight, or readability.
But strictly based on features and performance, which framework is better suited for an app with the following characteristics:
Tons of very similar views with nested subviews.
Lots of complex data to display and sort and update.
Backbone by itself is just a library to create your own framework, whereas Ember is a full-fledged framework for building apps. If you were to go with Backbone I would suggest something like Marionette. That being said, if you're looking for a framework where almost everything is already done for you and you just want to crank out screens, Ember makes this task fairly trivial. The complexity with Ember happens when you want to do something the non-ember way, in which case Backbone can allow for more flexibility.
From what you said it sounds like you are tasked with something that is large, but most of the work is fairly repeatable. I would probably go with Ember if that is the case.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
We have an existing Rails 3.1 consumer-facing web app and are reworking the UI to be far more interactive, snappy, app-like.
We have a modestly complex data model, but there's only a modest need for form-based user input.
We use jQuery now, with plugins to do nice effects, but overall, our JS skills are weak.
Our primary objective is to find a framework that helps us structure and organize our JS code and simplify the cases where we do have data bindings, AJAX, etc. in our Rails 3.1 world.
We'll learn how to do JS properly, but while we do, is there a clear framework we could learn and work within?
I don't know Dojo, but Backbone vs Knockout is a bit like comparing apples to oranges.
Backbone provides a structure for a web application + synchronization with the backend, whereas Knockout drives UI updates. There is some overlap between the two, but it doesn't mean they are actual competitors. There is even a project that tries to combine both - Knockback.
Last but not least, there is a great discussion on Bb vs Ko.
EDIT: I've just found this: http://addyosmani.github.com/todomvc/ - a comparison of different approaches to creating the same TODO app.