Answer the question
In order to leave comments, you need to log in
What is the niche of js frameworks?
In job descriptions, even for a backend programmer, knowledge of at least one js framework (angular, backbone, knockout) is often indicated in the requirements.
On the one hand, I understand that it seems that at least one of them is worth mastering in order to be in trend.
On the other hand, I look at the projects I dealt with:
- "Regular" sites (business cards, landing pages, online stores, etc.). Most of them do not have particularly complex logic on the client. jquery covers 100% of all needs
- Web services. Everything is clear, to drive XML / JSNON here and there, JS is not needed at all
- Web applications. As a rule, sets of grids with various filters, exporting reports to Excel, building graphs, charts. But DevExpress (for NET developers) or ExtJs are good for these purposes.
Here I sit and think what types of projects should be in which the use of frameworks would really be justified, and not just a framework for the sake of a framework. Something like Google Docs?
PS Googled the site https://builtwith.angularjs.org , but, in my opinion, most of the examples do not have particularly complex client-side logic, which is just what a framework is needed for.
Answer the question
In order to leave comments, you need to log in
well, for example, google music is written in polymer
, as for builtwith - it’s like yes, you usually get a little disappointed when you look through this case, there are only a couple of interesting projects and everything else is something simple.
what are web services for you and where do you "drive json" from? Do I understand correctly that you are now talking about microservices on the backend? What about the frontend then?
Stop thinking with desktop interfaces from the early 2000s. Personally, I think grids are bad form (with very few exceptions, lists do a much better job of displaying information).
Yes, in fact, any single page application, because the framework (for example, the same angular) gives you a ready-made infrastructure that allows you to isolate everything in layers, make isolated and easily covered by tests (you won’t ask why tests are needed?) interface elements. And the business logic on the client is overwhelmingly simple, usually everything rests on the UI and how to organize this whole thing. Frameworks make development much easier.
Well, a decent number of hybrid applications (cordova / phonegap) have been made on angular (or rather on ionic)
The article describes where blog.livecoding.tv/2016/07/06/top-10-js-frameworks are used
PS Googled the site https://builtwith.angularjs.org , but, in my opinion, most of the examples do not have particularly complex client-side logic, which is just what a framework is needed for.
The Backbone.js + Marionette.js stack is very good for developing large SPA web applications like ERP/CRM/CMS. Although, recently React has begun to taxi in this area, due to the easier implementation of the isomorphic approach.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question