Java，。 Net, I have a lot of confusion about the specific definition of the front end. For example, HTML and JS definitely belong to the front end. Yes, then sing.

Front-end and back-end are not standardized names, but nicknames for convenience. They can also be called foreground and background, right?

The distinction in the traditional sense is still relatively clear: simply speaking, it is B in B/S architecture, that is, the front end, that is, the browser end. From the point of view of post, the person who develops web pages in the browser can be called the front end (this is a common usage).

If you want to know more about the technical differences, you can consider this. The code is interpreted and executed by the browser, that is, the front-end HTML, js and css, and nothing else. What the browser doesn't execute is backend, jsp, php, servlet. .....

However, with the continuous enrichment and development of technology, these meanings have changed.

The environment of front-end execution becomes complicated. For example, html5 can run in computers, mobile phones and browsers. Not just in the browser.

The front-end communication protocol is not only http, but also websocket, sse and so on.

There are also some languages that take all sides. For example, js is undoubtedly the front end in traditional applications, but now it is hard to say that js can't do the back end.

That is to say, the front-end is no longer limited to browsers, but more and more like C/S architecture.

Therefore, it is more appropriate to use client and server to understand front-end and back-end.

Similarly, determining the ownership of a technology depends on whether its code is executed on the client or the server.

In addition, the concept of back-end has become blurred, because of the development of technology, the server has gradually separated from the traditional single architecture, such as micro-service.

So I think this concept should be a joke. There is no need to struggle.