A
A
Alexey Kostyukhin2019-04-30 14:14:26
Frontend
Alexey Kostyukhin, 2019-04-30 14:14:26

Why do we need a frontend, if the entire stuffing of a site or a project can be implemented using the backend?

The question will seem inappropriate to many and generally stupid from a technical point of view. But in fact, you can implement the entire interface using the server side. Write logic on it, then an interface, add animation, make page layout, etc.
See for yourself. All global web projects that exist are implemented using the server side.
For example: search by image. Implemented with python.
2. Neural networks: if there is some function on the site for statistics, etc. To convert simple children's drawings into works of art - all this is implemented on the server side, using server languages. Such as phyton, node.js, PHP
What are languages ​​such as JavaScript, HTML, CSS and the like for?

Answer the question

In order to leave comments, you need to log in

9 answer(s)
N
nrgian, 2019-04-30
@nrgian

1) "Everyone on the server" - this has already been done. Since the dawn of the era of the beginning of the availability of computers. Google dumb terminal. And until recently, they existed in wide use in some places, despite web technologies. For example, in France.
2) Nobody bothers you to write both the server part and the client part in Python.
3) JavaScript, CSS, HTML - this is simply because instead of installing a separate program on the user's computer for each server, they came up with one common program - a browser, within which clients for various servers are already being implemented. Well, historically it so happened that only these 3 languages ​​​​are supported inside the browser today. If you do not want to use these languages, do not want to use a browser - then see point 2)

S
sharpross, 2019-04-30
@sharpross

JavaScript, HTML, CSS - To arrange the information coming from the backend + reduce the load on the backend.
We can render pages on the client immediately and gradually load only the necessary data from the back.
As a result, the server gives a minimum of information, otherwise the server will still have to spend time rendering a new page with each request.

V
vgorbatenko, 2019-05-01
@vgorbatenko

That's right // all the filling of the site should only be implemented on the back // don't listen to anyone // do it.

D
Dima Pautov, 2019-04-30
@bootd

JavaScript, HTML, CSS - in the browser are needed in order to visualize your data for the user, and phyton, node.js, PHP are needed in order to provide this data
1)

such as phyton, node.js, PHP
- node.js is JavaScript
2)
then the interface, add animation, make page layout, etc.
- and what are you going to build it on, except for JavaScript, HTML, CSS
All the current beauty of react, vue, angular interfaces gives us the opportunity to delimit the load. Let the server do what it should, logic and calculations. And the browser, based on the backend data, draws pages for us. Thus, we free up a lot of resources for the server so that it does not generate all this.

V
Victor, 2019-04-30
@DarthVictor

What a fat mess. Even if I now propose to abandon the backend and send sql queries directly from the browser, it will not turn out so thick for me.

L
lukoie, 2019-05-01
@lukoie

This is necessary to transfer part of the functionality (read the load) to the client.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question