Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
The title may be misleading many, so let me rephrase. What is the best framework or language that is used for displaying real-time data, that requires a lot of UI/backend rendering?
Recently I was using mean stack with angular2 for a project and it was very cumbersome for always using two-way data-binding or using event emitters to watch any change.
Is there any language/framework that just renders UI based on what has been changed in backend or frontend?
Would reactjs or metoeorjs do the job?
Please enlighten me.
Thanks
I'm unsure of what would have changed with Angular2 but Angular JS was developed to among other things, make something like that easy.
Since Angular 2 has added much more and streamlined how things are done I'm going to say you don't have a good grasp on what the capabilities are because that should be able to handle that. If not, then Angular JS(1) can for sure.
A lot of people are straying away from Angular due to the huge changes in 2 in my experience.
Personally, I use react to do this. If you set up web sockets, or use Firebase all you do is handle the event triggers. When they do, react uses immutability to see what part of objects have changed and renders/updates elements accordingly.
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
I know that for a simple static website, using plain HTML.. is the easiest and quickest way. But, what are some use cases between the two options? Is using a framework mostly the best solution?
You can basically see frameworks as pre-written structures for your App.
In other words, frameworks are meant to help you building applications quicker by addressing common development problems.
So, going back to your question, there are not really times where you would prefer vanilla javascript over frontend frameworks due to the incapacity of scaling well, which could result in inscrutable and unmaintainable spaghetti code.
Other bit you would want to consider about frameworks, is their high performance obtained thanks to their virtual DOM (abstract map of the real DOM), which helps handling events to update parts of the App without the need of re-rendering it.
On the other hand, I would suggest to go with a static website using pure HTML and Vanilla JS, only if learning / instructing someone, or if building something really really simple (but rest assure 99% of your commercial websites may suit better under a framework rather than without).
If you want to read more about it, I would suggest the following articles:
https://stackoverflow.blog/2020/02/03/is-it-time-for-a-front-end-framework/
https://gomakethings.com/why-do-people-choose-frameworks-over-vanilla-js/
https://www.freecodecamp.org/news/do-we-still-need-javascript-frameworks-42576735949b/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
New to front end development here. Discovered Yeoman, seems like a great tool. I worked through a tutorial and then completed a small project using Angular JS with a Node JS backend. To assist in looking at things from my perspective: at this point I don't know enough web development to abstract my approach, I just know the set of tools I can use to get something working. I know if I want to make a new web site I can generate a project using Yeoman, fiddle with the HTML/CSS, and make the content dynamic with Angular. It actually works pretty well.
However, I am curious as to what the other approaches to web development are. What are the alternatives to Angular JS? Is Angular.js the standard/common approach?
There are tons of Javascript frameworks out there. AngularJS is quite popular, but by no means the standard or common practice. Other popular frameworks you may want to look into are Meteor for full stack apps, ReactJS, Backbone, Ember, and many many more for front-end Javascript frameworks. Also, taking a step back, there are tons of other approaches to web development other than just considering what's on the front end (HTML, CSS and JS). For example, you can build whole websites without even touching javascript using Ruby on Rails. Other big frameworks are Python's Django, PHP with Drupal, Wordpress, Joomla, etc., and .NET / C# just to mention a few. Hope that gets your research started.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Improve this question
I am building a Web app using AngularJS, and I am finding it difficult to choose between ng-router and ui-router.
It's kind of a big project and I can't make a wrong choice; could you help me take the right decision?
ngRoute is an angular core module which according to me is good for basic scenarios. On the other hand ui router is a contributed module which has overcome the issues faced by ngRoute. ui router becomes more powerful when it comes to handling complex nested views. So for a big project you should go for ui route as it may become complex after sometime to handle the views.
According to John Papa and his commonly accepted style guide, "ui-router" is the router that you want to use:
Why?:
UI Router offers all the features of the Angular router plus a few
additional ones including nested routes and states.
The syntax is quite similar to the Angular router and is easy to migrate to UI router
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 was playing with ReactJS for a bit, and given a bit of prior exposure to AngularJS, and the way things are done in the latter, I had a hard time to get used to the syntax and the 'flow' of React.
So I had the above-mentioned question, plus: are there scenarios when ReactJS should be preferred to AngularJS?
Could anyone point out what can be done [easier/better/more efficiently] in React rather than in Angular, and other way around.
It's actually the opposite. Angular has a lot of features, apis, configuration options, etc. React tries to be much simpler and let you choose how your application is structured. Controllers, directives, and templates are reduced to just components. Services are just plain JavaScript, there's nothing React specific about it. Things like $q and $timeout don't exist because there's no digress (use anything you like for those).
You use React in your application, vs making your application in angular.
ReactJS uses the concept of virtual DOM which speeds up the rendering of the app.
Watch Pete Hunt's excellent video on Virtual Dom here:
https://www.youtube.com/watch?v=-DX3vJiqxm4
The syntax might be very unconventional but the same thing can be said about Angular's concept of Directives, services, controllers, etc. It just takes time to get used to, but once you feel comfortable, you'll find that thinking in ReactJS really makes sense.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm migrating from Solr to Elasticsearch and was wondering if there was a UI available that is similar to Solritas. There is a great tool here:
http://mobz.github.com/elasticsearch-head/
Which provides browsing/searching capabilities, but it doesn't seem to have faceted browsing implemented yet (please correct me if I'm wrong). Is there another UI that is popular with elasticsearch, or would I be better off implementing something using the extensive client apis?
Thanks,
Saw this recently. May be a good starting point for what you're looking for: https://github.com/okfn/facetview
Kibana is coming along nicely. It requires a bit of customization to get it the way you want it, but it's built from the ground up to work with facets.
There is no better UI available for ES as ES-HEAD is already great and steadily improves.
But maybe this is the perfect solution ;)
"why not contribute to that project, implementing facets and sending a
patch / pull request? – Mauricio Scheffer"
Link to source: https://github.com/mobz/elasticsearch-head
You can use Sense(Beta) extension of chrome browser.
ElasticSearch data browser
Search, charts, one-click setup....
Take a look at Calaca, it's a simple, yet good looking, search UI for Elasticsearch and with minimum configs required to get started. It doesn't support faceting though, but if all you need is simple search and browse, then this might work for you. On github - https://github.com/romansanchez/Calaca