Whether the back-end development is more conservative than the front-end?

In recent years, often hear developers complain about how much they need to know to work successfully: technologies, frameworks, programming languages, tools, etc. In my experience I can judge, a direct impact on front-end development - a whole heap of js-frameworks that appear almost every day, css preprocessors, build systems, bootstrap, graphic editors and so on. But as for buck, the picture is not that scary - well enough to know 1-2 of the framework, DBMS, and have the skills to work with the server. Everything else is on demand. And watch for updates only of these technologies. Whether so it actually?
September 26th 19 at 20:09
12 answers
September 26th 19 at 20:11
Half of the answer is in the question, but the devil is in the details.
Indeed, for a relatively productive backend development in almost any programming language you should know a few basic frameworks and bodies that solve most of the problems. This skeleton ~90% applications more complicated hello world. Although this skeleton is changing and evolving, albeit not as fast as we would like, as a variety of processes (not conservatism, but a longer life cycle). The total weight of the technologies and tools no less, and certainly no less dynamic than that of frontend-developers.
Further personal experience on the example of Java.
7-8 years that it was enough to know Spring, Struts, Hibernate, Apache Commons Yes, in addition to develop most of the decisions. Well, J2EE stack for tasks Enterprise-level.
In year 2014, Spring, Hibernate still in the Arsenal of the programmer, but there was a lot of brand new things like AMPQ, Hadoop, Netty, Scala, functional paradigm, multi-language environment with Clojure/Groovy/JRuby; were more likely to meet alternative implementations of popular libraries (e.g. Guice / Guava); old technologies like J2EE were used slightly less often. And only one Key-Value storage, caches, and other NoSQL like dirt. Even changed the approach to building applications – in 2005, few people heard about asynchronous event-driven model and start from when designing a REST-style (in fact that is where the roots of the frontend developer as a separate specialization). About the evolution of build systems, VCS, benchmarks and other micro-elements, it is possible to paint more than one sheet.
And forgive me frontend comrades for perhaps swaggering tone, but to smoke the intricacies of async IO depending on the OS-specifics like epoll/kqueue or to consider the CAP theorem when building the middleware-cache is a level of complexity higher than the new CSS preprocessor and c another CoffeeScript MVC / MVVM framework. Some tasks, like synchronization of threads, and generally lie mostly in the field of mathematics.
I am sure that in frontend development there are tasks more complex and interesting go to the pixel layout and update the fields after the parsing of JSON, but IMHO the backend development closer to system programming old school, while the frontend application programming essence with a touch of design.
Frontend tools more backend-tools more difficult.
Yes, and this choice burden, purely on psychology - Jessyca.McDermott commented on September 26th 19 at 20:14
here, the last phrase - the first thing that came to mind ) - Cielo_Corkery commented on September 26th 19 at 20:17
And so it was until recently, when the power of modern home computers and the resources that they provided the browsers were quite small. And now we already have offline web applications web workers (full multi-threading in the browser), without the heels and minutes adopted the concept of relational databases in the browser (and implemented by all the major players), has long been living nosql database; the main language the front-line development (JS) contains the above-mentioned paradigm of OP, SOP, OOP, and other there. Of course, according to the cleanness of syntax to Scala or F# does not make it, but still...
Of course, a spherical front end in a vacuum never faced with the requirement to render a 10K tables in the eighth donkey (the problem also lies in mathematics :D) or write the stack machine - but the joke is that Beck is the same. Now for the vast majority of programmers on that front that the buck requires knowledge of five or six technologies. Rather, it is important not to follow ALL the news, but to be able to distinguish a hidden gem.
IMHO. - Aniya_Friesen4 commented on September 26th 19 at 20:20
good answer) - Jessyca.McDermott commented on September 26th 19 at 20:23
September 26th 19 at 20:13
I would say so - in the backend you can afford to be conservative compared to the front end, because the ordinary customer do not care, how does anything, it is important that how it looks. Therefore the frontend needs to "follow the fashion", and the backend need to be able to do anything with any of his usual tools, minimally appropriate, i.e. adapted to new items is not necessary.
Similarly, the client will not distinguish the front and the front from jquery and angular. - Jessyca.McDermott commented on September 26th 19 at 20:16
well, apparently the customer can not be distinguished - basically do not care)
but the frontend looks engaged, I about visual modnosti. the front end should catch up to the realization of fashion designers of chips. - Cielo_Corkery commented on September 26th 19 at 20:19
for example? - Aniya_Friesen4 commented on September 26th 19 at 20:22
en.wikipedia.org/wiki/Parallax_scrolling#Parallax_... - Jessyca.McDermott commented on September 26th 19 at 20:25
September 26th 19 at 20:15
I understand that a year has passed. Will enter his mind.

Technology stack for backend and frontend is equally challenging. A lot of decisions, a lot of subtleties. As web full stack
I know whereof I speak.

From my point of view, the development of the backend part is in a stable environment. On the server you can control the versions of packages, so if there are no errors in the code of the web project it can work long time without changes. The developers can install a virtual machine environment, close to the server. The result is that will work with the developers, will work on the server. In this sense, the development of server-side not that conservative, but more predictable.

The frontend task is more difficult - each one on its powerful computer in their favorite operating system, with a properly configured firewall, with fast Internet for your favorite browser latest version, writes code that must run on a huge variety of platforms with an incredibly wide variety of configurations. It may break suddenly, individual users on any of the latest version of a rare browser with slow Internet, via cruel-caching proxy server. It is very difficult to predict and very difficult debajit. Up to remotely connect to the computer of an individual user.

On the other hand, portfolio frontend developers full of beautiful screenshots of finished projects, sometimes even references to the running projects. Backend such beauty can not boast - sphinx, memcache, mongo/redis, mysql/postgre, php/python/ruby well or something - I mean, I have only the stack technologies to mention. But if in the portfolio, and will the screenshots, only to say later: there, in the shade of beautiful interface, stable and quick running my code.
September 26th 19 at 20:17
September 26th 19 at 20:19
I personally think this applies to industry in General.

In the backend it is actually even worse in my view. Because the web frontend, you only have HTML, CSS and JavaScript. In the backend you can use any language, plus, DBMS and other applications (web server, all the caches, bus, etc.). So the problem at least likewise frontendname multiplied by three.

If you want relative stability, take, say, Java, and area - UI or the web, and pretend nothing else for you there. Even thus restricting the flow of information can easily drown.
"on the web frontend, you only have HTML, CSS and JavaScript."

Well, of course))) You are far from the subject, I think - Jessyca.McDermott commented on September 26th 19 at 20:22
what else? - Cielo_Corkery commented on September 26th 19 at 20:25
September 26th 19 at 20:21
It seems to be true, isn't it? What you can't see ordinary users should not reply fashion.
So in your opinion if it is or isn't it?) - Jessyca.McDermott commented on September 26th 19 at 20:24
Partly Yes, but, on the other hand, front-end frameworks, preprocessors, build systems, etc. ordinary users do not see. - Cielo_Corkery commented on September 26th 19 at 20:27
I agree. You understand about what part of the front-end I'm talking about. And you know, one pulls the other. There are new features, with partial support, they pull over a some autoprefix, etc. - Aniya_Friesen4 commented on September 26th 19 at 20:30
I think that's true. But back-endщикам not myself, so my words may have 4 to share. - Jessyca.McDermott commented on September 26th 19 at 20:33
September 26th 19 at 20:23
well, not to say, languages have multiplied
ruby Python PHP
all the different versions
the node sorts its counterparts
database breed
nosql etc
well, in General, a significant evolution in the backend more substantial than in the front
So you can select one language-framework and work in peace. And in the front one jquery is not limited in any - Jessyca.McDermott commented on September 26th 19 at 20:26
all of it js
as well as the php programmer have to work with different frameworks
overall, the layout has already happened what the canons say and 90 percent of the sites used the same jquery - Cielo_Corkery commented on September 26th 19 at 20:29
on the front you can use angularjs and sass all, nothing else - Aniya_Friesen4 commented on September 26th 19 at 20:32
Pro counterparts node would listen - Jessyca.McDermott commented on September 26th 19 at 20:35
: well Google counterparts node - Alexandra_Green commented on September 26th 19 at 20:38
September 26th 19 at 20:25
And Yes start holivar!
September 26th 19 at 20:27
Bekendste dumb to admit that all their work is an analogue of cout<<"hello world :-) :-) :-)

And in fact, the frontend is the "what, where & in what form to withdraw and prenatt response", and the backend is only the "what to bring".
What is it? - Jessyca.McDermott commented on September 26th 19 at 20:30
The man apparently anything more complicated than a blog is not seen, or just a Troll =) the Frontend is just a wrapper, beautiful (or not) packaging, the main business logic of the application is always focused on the backend for a number of reasons. - Cielo_Corkery commented on September 26th 19 at 20:33
September 26th 19 at 20:29
Yes, in the frontend, BUT!
I have a programming experience how to find out e (Java, PHP, Go, Node.js) and front e (JS, HTML, CSS) and that's what I say.
Take SASS. I studied for the day. A little more. Shoveled the docks, do examples for zakrepleniya
Now, take the same Java. Spring Framework, for example. Program it a little more than six months. Even close can not say that you know all its intricacies. That makes all the difference. No need to look at the number freimark & tulov in one area or another. You need to approach the issue from the point of view of investment time.
With Java frameworks better to compare js frameworks (the same angular). And sass it as some kind of template engine like twig for php, which is also the day studied. - Jessyca.McDermott commented on September 26th 19 at 20:32
September 26th 19 at 20:31
in the frontend enough to know jquery or angular or any other at your choice, different css preprocessors and css frameworks to learn in 2 and a half days, in the backend all sufficient elainee, it is impossible to solve some tasks with one tool, you need to know, a database several mysql, mongodb, system caching, redis, memcache, work with Linux, not with one version of ubuntu, maybe centos and several frameworks, which also churned out every day, the same build system, deployment, systems asynchronous tasks rabbitmq, celery and even wonderful all sorts of things to follow the updates even a single framework problematic, not to mention a few.
I would argue) You my version with the head turned)) to Complicate your design, you can always, but not everywhere it is justified - Jessyca.McDermott commented on September 26th 19 at 20:34
The question is not that complicated, and conservative. Do you think that tools back-end are more susceptible to the changes or not? (I'm not arguing with You, and clarify) - Cielo_Corkery commented on September 26th 19 at 20:37
for example some frameworks that are churned out every day? Enough to know any Yii or Django at a good level and grief do not know. DBMS and operating systems - here you can choose one or the other - Aniya_Friesen4 commented on September 26th 19 at 20:40
on the front is enough to know at a good level angularjs and everything and nothing else - Jessyca.McDermott commented on September 26th 19 at 20:43
September 26th 19 at 20:33
Frontengine climbed on to the server through the window Node.js and bridge JavaScript and spawn 80k packages, the heat is gone, it can withstand... https://www.npmjs.org/

Find more questions by tags ProgrammingBackendFrontendWeb Development