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
This is kind of an unusual situation so forgive me for the odd title. I've been looking at optimizing an HTML interface for manipulating server data. All data is passed over a REST service and there are existing jQuery methods for pulling and submitting the data.
The problem is that all this runs very slowly due to the large amount of Javascript code used for animating and manipulating the screen. Obviously I can optimize the javascript code to some extent, but the interface is so slow I'm wondering if there are other frameworks I should look at taking advantage of. I don't have the ability to leverage anything server side like PHP.
If there are no other frameworks, I'm planning to move most of the code to jQuery to improve readability and take advantage of the optimizations others have done there.
Please have a look at AngularJS. It is a framework (by Google) specifically designed for data driven websites. It is built on jQuery. It provides a $resource service which can be used to develop your own REST client for your website. The purpose of which is to enhance code readability and performance by abstracting the lower-level HTTP calls.
You can also have a look at Dojo but it has a huge learning curve.
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 6 years ago.
Improve this question
Meteor.js integrates well inside a Mantra.js architecture, but does it have advantages since it slows the running of my requests.
For instance a dummy request in GraphQL (get a random string from the server) runs in few ms using Apollo Client and 1 second and more using Mantra.js (exact same request wrapping Apollo stack).
It only depends what kind of project you want to work on.
Mantra.js is an architecture framework for Meteor.js, that means :
it helps a developer to follow the creation and development of its modules corresponding to the Mantra framework. The developer is free to use any kind of front-end library he/she wants, any Data Query and Client caching he wants, but in my opinion, it doesn't really improve the quality of the code. Someone can organize a project with own rules and it can be maintainable easily.
So if your team is comfortable with your code structure you definitively don't need something like Mantra.js.
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 a project implemented using ASP.NET MVC 4. it is a multi page application.
We use jQuery for handling client side interactions. Now the js file has a lot of callback functions. Is there a better way to define and manage them?
Can you suggest any js library to define these callback functions and to handle the response from the server?
I have gone through backbone js and knockout js. it has been mentioned that it is extremely useful in organizing single page applications.
Would it be helpful in our project (which is a multi page appilcation) or will it cause an overhead?
I think this will be useful,
Node.js: What techniques are there for writing clean, simple callback code?
See "Trevor Burnham" answer. Also see the links given here.
I am not understanding your question clearly. Are you looking for reduce the no of files? what you are mentioning here for the term Organize. Here i added points for improving performance
Hope this will be useful,
Make the repeated functionalities as a common function and differentiate with various parameters or flags.
Reduce the new variables creations mostly.
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.