The term "Front-End" is wrong, but we still use it

As much as the term "Front-End" is extremely popular today when it comes to the developers of HTML and JavaScript for a given website, the context of its origin is quite different from that term.

In 1998, it was common for all fans of Internet Explorer 4.01 that accompanied the version of Front-Page Express 2.0, alongside Netscape that also had its HTML editor (practically built-in), to make some kind of page and publish in some service accommodation.

It turns out that it was so "easy" to make a website, that it didn't need any knowledge of HTML, of course, except for some elements where I could put custom scripts with JavaScript code or even extending VBScript for front-side, but the big question is that the ease, generated a problem in the name, and many online sites made in these softwares.

A professional who makes a website, should be a "Front-Page Designer", or also "Front-Page Developer", or at most "Front-Side Developer", which would be the most obvious in contrast to "Server-Side Developer" , which is responsible for internal programming not seen on the web.

The term "Front-End" came about by HTML and JavaScript developers who make the code in a professional manner, and who did not accept the comparison of their work with the "Front-Page" existing at the time, brought by "Front-Page Express" , and its successor failure "Microsoft Front-Page 4.0".

That is why, until today, we have the term "Front-End" and, by the way, we do not generally have the term "Server-End", which would sound very strange.

If you are a "Front-End" developer, fine, we know that you do not use Front-Page in your projects, but it would not be more convenient to refer to "Front-Side", since you work on the front side of a site?

Think of the idea. See you.

No comments