What is "100% JavaScript front-end"?

Question

JavaScript

Hey!
The phrase “100% JavaScript front-end” came across several times ... we, they say, “100% JavaScript front-end”. Or "requires a 100% JavaScript front-end developer". Or even “100% JavaScript front-end framework”.
Who knows what kind of beast this "100% JavaScript front-end" is? And exactly 100% . Without them, at the very least, I imagine JavaScript front-end as a front-end pumped up with all sorts of jQuery, Ajax, and other webdulls, etc., etc., but it’s 100% that confuses me.
Help eliminate this shameful void in my experience (:
Thanks in advance for intelligible answers.
Thanks for participating, comrade k12th won .
He gave, IMHO, the most accurate answer with an emphasis on raising the question of 100%. Without these 100%, you can procrastinate for a long time, but now everything is clear with them. / Applause /
Dolios , Your comment is also very useful, thank you.

Answer 1

eycharskiy bulshchit, IMHO.

Answer 2

Most likely, this refers to a frontend written in ExtJs or Qooxdoo, when there is 1 html file - index.html with an empty body, and all content is generated by javascript, i.e. R.I.A.
But I could be wrong, because I'm not a telepath.

Answer 3

JavaScript programmer who doesn't touch the server side. There are projects where JavaScript is much more than a server-side language. For example, Gmail ... somewhere they wrote that 80% of their code is in JS.

Answer 4

In general, it means that a person does not need knowledge of server languages ​​and he will only work on the client part.

Answer 5

Most likely when there is one div empty or generally just a body. And then with the help of similar constructions, the whole code is drawn.
var teg_div = $('<div>123</div>'); var teg_a = $('<a href="#">123</a>').appendTo(teg_div);
If you use, for example, Backbone with some kind of template engine, then someone will probably also say that this is 100% js code.

Answer 6

k12th is right :)
But, most likely, it means the situation when you have index.html (or not index, but html) and you have to make a whole website / applications from this file using javascript and a bright head without using a server programming language.

Answer 7

This is when you write code a la GWT, I guess. That is, everything is on the client side, there is no interaction with the server, there is no HTML - the controls and layout are generated by the script, and the styles are written by someone else.

Answer 8

This is when only javascript is responsible for the view. More specifically, this is when the server code is a classic model with a front controller, without any templating and other things. The server only sends data. And Javascript completely renders the page based on the data received from the server. It turns out that about 80% of the code and logic of the entire application is in JS. It was rightly noted here that gmail is one of such applications. Roughly speaking, when index.html is loaded, there is nothing in it except the JS application.
I did enterprise-projects of this type for 4 years, when I left that company I no longer found offices dealing with similar ones, although I went around about 15 companies in Kyiv and Dnepropetrovsk. In general, if you want to go on the web, then I strongly advise you to go for such a project, because this is a unique experience + you will become a JS programmer, not a jiquery boy. Before I started working with js, I knew C ++ and a little php + html. Now, as a senior dev involved in Javascript (but mostly Node and smartTV), I get more objective C programmers of a similar level. And just because 90% of JS programmers don't even know a single principle of software development, not to mention creating applications is more difficult than screwing dynamic elements to ordinary sites.