How to decide on a framework?

Question

Angular

Need help with choosing a future development path in web development. So far, only HTML / CSS / JS has been behind.
I can choose it, but for this I do not have enough understanding of the "full picture of how everything works."
Basically, the options are:

1. Client side with Angular || React || Ember
   
2. Back end with ruby ​​and rails || node.js with sails and similar || python with django…?
   

It’s not clear to me, this is the division of frameworks into groups, what do they do and what tasks are the frameworks from the first group and from the second intended for?
Why are they so divided?
Are they used together, or just one?
What tasks are solved by frameworks from the first and second groups?
For which task will it be enough to know only Angular, and for which only rails?
Like a big sea in which islands are visible, but there is no whole map, which does not even occur to me how to ask the right question in order to understand;

Answer 1

It’s not clear to me, this is the division of frameworks into groups, what do they do and what tasks are the frameworks from the first group and from the second intended for?

1st group works on the client (in the browser)
2nd group works on the server
Different execution platforms
Depends on the project.
1st BL (business logic) for display and interaction with the user
2nd BL for data processing and interaction with the client (browser)
Angular only - frontend tasks
Rails only - backend tasks

Answer 2

Need help with choosing a future development path in web development.

For starters, don't get hung up on the framework. This is just a tool, a useful tool that is worth using, but you need to understand why each of them is needed. In an ideal world, the bulk of your application is separate from the framework, but... in an ideal world...
division by programming language and tasks that this framework solves. Let's say RoR, Sails, Laravel, Symfony, Drango are frameworks for organizing a WEB interface to your application. And no more.
Angular, Ember, React, etc are frameworks for organizing interactive WEB applications on the client, they have nothing to do on the server (if you do not take into account server-side rendering to speed up page display).
if you need to write an interactive application and an API for it, then it is logical to take two frameworks that implement what you need. So yes.
draw. We put the WEB in the center, branch the client and the server from it, and connect everything ... Wikipedia can help us with this.

Answer 3

can be divided by technology into php frameworks, javascript frameworks and css frameworks, etc. Traditionally, the server part is written in php, and the client part in javascript, all this is decorated with css.
But you can get by with one, you can use several. The choice of quantity and types depends on the project. For example, I do most of the projects in php framework yii2 and css framework bootstrap3, which is connected there out of the box. A completely self-contained link. And while yii2 is php and bootstrap3 is css , they have a bunch of javascript (jquery to be exact) tricks. So there are no clear rules and boundaries. The best way to understand is to start doing. Get yii2 and give it a try.

Answer 4

It’s not clear to me, this is the division of frameworks into groups, what do they do and what tasks are the frameworks from the first group and from the second intended for?

The first group - frontend - frameworks working on the client side. Those. in the browser
The second group - languages ​​+ frameworks for the backend - the server side.
There is 0 common between them, these are completely different things for different tasks.
If you mean whether to use Angular and Ember (or Ruby on Rails + node.js), then the answer is 100% no. These are interchangeable items.
The first group deals with the user part. Renders Dom, performs client calculations, Ajax
Second - server frames. Based on them, the site itself is written, its basis. Or REST.
These are not mutually exclusive things. Angular renders the client, updates fields, html, sorts tables. RoR responds to post/get, acts as REST.
To summarize, if knowledge is 0, start either from the frontend (group 1) or from the backend (group 2). Often this is a different way of thinking.
If there is no knowledge even in JQ, but you want to take a site for a start, take JS + PHP (but quickly quit as soon as the skills appear). After that, switch to Coffee (js replacement) + Node.js
References in Siberia:
PHP
node.js
jquery.com
coffeescript

Answer 5

To in one cynical and obscene joke about the waiter: "take the 'old miller' ...".
To paraphrase - meteor zhs - your choice.

Answer 6

The situation is this: "While we were harnessing the horses, the world came up with rockets and flew to Mars."
You should always use the technology that you are very good at. And point.
Frontend frames are roughly equal, you don't need to separate them. Anyone will do.
As for the backend, it can be divided into 2 groups:
- A regular site or a spa (everything will do here, and hack and python and a node and cheat.)
- Where hard real multithreading is needed (for streaming any garbage in the style of video or music) - here is a question for masters of Erlang or Go and other "tanks".