Analysis of world scientific views International Scientific Journal 2024

Vol2 Issue 1 IF(Impact Factor)8.2 / 2023

THE ROLE OF FULL-STACK PROGRAMMING ON
THE WEB IN 2023
Mamadjanov Shuxratjon Shavkatovich
teacher of business department of Kokand University,
[email protected]
Kokand University KI-1-22 group, student,
Olimov Ilhomjon
+998336889339

Annotation. This article provides information on web dating languages and

their technologies.
Keywords: Html, Css, Javascript, Api, Node js. Frontend, Backend, Spa,
React, Java, Ruby, Postgres, JQuery.
Introduction.
It is not a question of what is better: a narrow specialty or a broad profile.
Let's talk about just one specific area - web development. Not about mobile apps,
machine learning, game development or anything else, just web development. Let's
start with a brief history of it: how it has evolved over the past two decades.
A look back in history: In the early 2000s, when the Internet was still young,
the divide between backend and frontend developers was almost non-existent.
Browsers weren't as powerful as they are today, and websites looked much
simpler. Some people specialize in HTML/CSS, but that doesn't count as
programming because... HTML is a markup language, not a programming
language. However, the industry was already very active. PHP, Java, Ruby,
JavaScript, CSS, MySQL, Postgres - all these technologies appeared in 1995-1996
and we continue to use them today. By 2000, developers were building enough
websites to cause a dot-com crash, and that was without even using jQuery!
2010s: Front-end frameworks enter the scene
The 2010s saw a big change with the advent of front-end frameworks. A vivid
example of demonstrating its capabilities in those years was Trello, a popular task
tracker announced in 2011. It was built on the Backbone.js framework, which was

https://academics.uz/index.php/awsit 5
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
the most advanced technology at the time. Trello was a "single-page application"
(SPA), meaning that most interactions with the server did not require a full page
reload. And it worked fast! Trello was so popular because of its smart design and
generous free plan that many people tried it, and many continue to use it today.
Trello was certainly not the first SPA. Another well-known example is
GMail, released in 2004. However, Trello is built on a front-end framework, and
frameworks promise to make building such apps much easier. The 2010s saw their
rapid flowering: the first releases of Backbone.js and AngularJS in 2010, Ember in
2011, React.js in 2013, etc.

API
The 2010s also saw explosive growth in APIs:

https://academics.uz/index.php/awsit 6
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
API
Many organizations have realized that building APIs saves development
effort and helps them move faster. The same API can be behind both a web app
and a mobile app, and if needed, it can be exposed and used for external
integration. The popularization of the REST concept has also fueled the growth of
APIs.
Backend or server side. This is the hardware and software part of the system
that is invisible to users: they do not know about the operation of internal processes
and cannot influence them. The backend is located on the server - a powerful
computer responsible for storing data and processing incoming requests.
Frontend and backend developers always work as a team. The frontend helps
users send requests to the server and receive clear, human-readable responses.
Backend creates the basis of the site: database, data transmission algorithms. A
front without a back is like a car without an engine: there's a steering wheel, a nice
interior, but you can't drive.
Main part:
Frontend developers
Frontend frameworks were very popular in the 2010s. They were talked about
at conferences. The "X number of days without new
frontend frameworks" joke wasn't such a joke back then.
Some web developers were excited about the
news, but others...not so excited. CSS and JavaScript
used to have a dubious reputation. Browsers were
imperfect and very incompatible, so a lot of CSS and
JavaScript hacking was required to achieve the same behavior in all browsers. Now
another layer of complexity was added - front-end frameworks, JS bundlers,
dependency managers, and it was all still young and buggy.
Some developers began to specialize in front-end work and called themselves
front-end developers. It seemed reasonable because the industry is growing so fast.
https://academics.uz/index.php/awsit 7
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
All of these added complexities took time to learn and developers were always
lacking. At the time, many "traditional" web developers retrained as back-end
developers and were happy that they didn't have to deal with the chaos of the ever-
changing front-end.
The API has become a natural boundary of responsibility between the
backend and the frontend. Back-end developers create an API, and front-end
developers create an application on top of that API.
Splitting into backend and frontend provides two important advantages:
Facilitate recruitment. Because the amount of knowledge required for each
role is reduced, it takes less time to train a qualified professional. Also, the division
into backend and frontend allows people to choose their preferred area. Some
people like to work with interfaces, others are closer to the backend world with
databases and algorithms.
Deeper specialization. However, as the amount of knowledge required for
each role decreases, people become experts in their field more quickly.
Some say the benefits may include faster and/or better quality work on a
project, but this is not always the case. In practice, there are cases where the effect
is completely opposite, and we will talk about them in the next section.
State of the art frontend
What has changed in the frontend since the 2010s? A lot of things, but the
most important thing is that during this time front-end development was
established and maturity increased:
New frontend frameworks no longer appear every other day. The industry
continues to innovate, but it's no longer the crazy rollercoaster of the 2010s;
Browsers just got better! We don't need a lot of CSS hacks in our codebase
anymore. Flexbox and grid layouts are already safe to use in most applications, so
we can finally center the <div>;
JavaScript has improved, and it's not just because the left panel is finally
included in the standard. Many improvements have been made to the language
https://academics.uz/index.php/awsit 8
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
itself, tools, frameworks, libraries, dependency managers, builders, linters, and
testing tools. And JavaScript is no longer slow - it's faster than many popular back-
end languages like Python and Ruby;
TypeScript is now the de facto standard for those who prefer more powerful
writing.
Of course, this does not mean that all problems in the front end have already
been solved, but it is much easier to work with it now than it was 10 years ago.
Yes, there's a lot of complexity here, but it's not as bad as it used to be, so now
backend developers have less reason to hate the frontend.
Why do you need full-stacks?
However, not everyone was in a hurry to separate
the backend and frontend. Along with front-end
developers, another role emerged - full-stack
developers. They were required to work with
both backend and frontend - just like the old
days, but using modern technologies. Facebook is a
notable example: there was a time when they proudly stated that they only hired
full stack developers. You can also find full stack positions at Google, Netflix and
other reputable organizations.
Why didn't everyone accept the split between backend and frontend? Well,
because it's not free. In addition to the advantages listed above, there are also
problems:
Additional dependencies. The division of roles into backend and frontend
creates an interdependence of developers. Frontenders need an API, but can't build
it themselves. They should first agree with the backers on what the API should be,
and then wait for them to do it. If they don't have other tasks yet, to avoid wasting
time waiting, they can create a fake API and work with it for now, then replace it
with the real API. If they later discover that something in the API is missing or not
working as it should, they should notify support and wait for it to be fixed.
https://academics.uz/index.php/awsit 9
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
Mediocre APIs often result from this noise. Sometimes front-end developers
find that the API they are using is not perfect, but at the same time they can work
with it by using some hacks. Of course, ideally, you should have reported the
inconvenience to support, but it's longer and more difficult than fixing it yourself,
so people often don't bother.
Especially in small communities, there are problems with the distribution of
loads. Load balancing is very easy with full stacks because any developer can work
on almost any task. The share of work between the backend and the frontend can
change throughout the life of the project, causing the workload of developers to be
far from optimal. It turns out that front-enders are overloaded with high-priority
tasks and back-ends can't help them, or vice versa.
Some technologies cross borders. Take SSR - Server Side Rendering for
example. The same code is executed on both the server and the browser.
Technically, it is closer to front-end because it uses frameworks that front-end
developers usually work with. However, in the case of SSR, frontends find
themselves in unusual territory - their code is also executed on the server. Another
example: Hotwire for Rails, introduced in 2021, offers an alternative approach -
creating interactive applications without traditional SPAs and APIs. Another
interesting technology is WebAssembly, which allows you to run high-
performance code both on the server and in the browser.
Lack of product thinking. Because full-stack developers work on all aspects
of a task, they have a complete picture of what they're doing. Front-end developers
see how users interact with the app, but they may have little insight into its inner
workings. Therefore, it can be difficult for them to determine what will be easy and
what will be difficult to do and how they can be optimized. Backenders, on the
other hand, have a good idea of what's inside, but they may not be looking at it
from the end user's perspective.
Need to hire full-stacks?

https://academics.uz/index.php/awsit 10
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
Depends on the project. If your project doesn't have active interaction
between the backend and the frontend, full stacks may not be very useful. At the
same time, it's significantly easier to find specialized front-end and back-end
developers, and that's important.
However, if the interaction between the backend and frontend is very active,
and many business tasks require work on both parts, it may be necessary to offer at
least a few complete sets to the team . They are more difficult to find, but it is
certainly possible. I know this first hand because we at ivelum have been hiring
full stacks for many years. If you don't believe me, trust Google, Meta, Netflix, and
others: competent full-stack developers exist and can be found.
Alternatively, you can have a hybrid team: part full stack and part split front-
end and back-end to get the best of both worlds.
SSR frames
Single Page Applications (SPAs) and their corresponding frameworks (e.g.
React.js, Vue.js, Svelte.js) have gone through more or less high-profile cycles and
have been around for years. However, with the advent of meta-frameworks on top
of these solutions, we can see the trend of applications moving from client-side
rendering (CSR) to server-side rendering (SSR). SSR is ubiquitous in JavaScript
frameworks today.
The most popular SSR framework called Next.js runs on top of React.js.
Andrew Clark, React's lead developer, called it a "true React 18 release" in 2022,
as it will come with all the built-in capabilities (e.g., Suspense, streaming SSR)
that the React team provides as basic building blocks at the lower level. . from the
library. Vercel (the company behind Next.js) and the core React.js team work
closely together to provide a great experience for developers.
While many developers are wary of the close relationship between Next.js
and React.js, there are alternatives to React.js such as Remix (recently acquired by
Shopify). Remix takes a different approach to making React.js an SSR framework,

https://academics.uz/index.php/awsit 11
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
but due to competition, both frameworks have similar features (like internal
routing).
While Next.js is already the recognized leader in modern SSR development
and has turned many front-end developers into full-stack developers, there are
other frameworks that should be on your list: SvelteKit ( Built in Svelte.js) with
Vercel's recent version 1.0. support and SolidStart (built on top of Solid.js) with
improved DX compared to React.js.
Types of rendering
Single Page Applications (SPAs) with Client-Side Rendering (CSR) from
Knockout.js and Ember.js to Angular.js, React.js and Vue.js in the last decade
(2010 - 2020) Although dominated, in recent years there has been a growing
interest in server-side rendering (SSR) with SSR frameworks. On the surface, the
loop seems to be closing again because we've been using SSR for a long time
(from 2005 to 2010) with JavaScript (eg jQuery, MooTools, Dojo.js)
implementations in multipage applications (MPAs). . However, if previously Java
(like JSP) or later Ruby on Rails was used, this time it is different because we rely
on JavaScript. For several years, Next.js has been the driving force behind this
trend, but other SSR frameworks like SvelteKit are also catching up.
SSR has long competed with static site generation (SSG) for ideal
performance, although both patterns serve completely different purposes. The latter
pattern is used for static content (such as blog-type websites), while the former is
used for dynamic content (such as web applications). If SEO is important, both
SSR and SSG can make sense. However, when faced with the need to create
dynamic or user-specific content with authentication, developers can't choose
between SSG (created once before deployment, so static) and SSR (individual per-
request ma will be forced to choose between server) and CSR (client-based custom
data retrieval).
Summary:

https://academics.uz/index.php/awsit 12
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
In the article, the concept of web programming and new technologies are
presented, the purpose of which is to get information about this field and then there
will be no problem choosing the web field.
References:
1. Davronjon, A., & Gulmiraxon, K. (2022). WIDESPREAD
INTRODUCTION OF DIGITAL TECHNOLOGIES IN THE REAL SECTOR OF
THE ECONOMY, AS WELL AS IN AGRICULTURE AND WATER
MANAGEMENT. World Economics and Finance Bulletin, 9, 167-172.
2. Abdullajonov, D. S. O., & Kasimova, G. K. Q. (2022). DEVELOP A
TRAINING PROGRAM FOR YOUNG PROFESSIONALS IN EDUCATIONAL
INSTITUTIONS, WHICH IS THE CORE OF CYBERSECURITY. Academic
research in educational sciences, 3(6), 185-192.
3. Shokirjon o‘g‘li, A. D. (2023). AXBOROT TEXNOLOGIYALARI
SOHASIDA ILMIY IZLANISHLAR OLIB BORISH TENDENSIYALARI. QO
‘QON UNIVERSITETI XABARNOMASI, 1223-1227.
4. Abdullajonov, D., & Qosimova, G. (2022). OZBEKISTONDA
KIBERXAVSIZLIK VA RAQAMLI IQTISODIYOT RIVOJLANISHINING
AXBOROT JAMIYATI SHAKLLANISHIDAGI ORNI. Евразийский журнал
математической теории и компьютерных наук, 2(13), 29-37.
5. Shokirjon o‘g‘li, A. D., & Solijon o‘g‘li, T. U. (2022). The Application of
Digital Technologies to Enterprises and Organizations Will Help Reduce Social
and Economic Costs. Eurasian Journal of Learning and Academic Teaching, 4,
131-140.
6. Abdullajonov, D. (2021). RAQAMLI TEXNOLOGIYALAR ORQALI
YANGI O’ZBEKISTONNING IQTISODIYOTINI RIVOJLANTIRISH,
RAQAMLI IQTISODIYOTNING ISTIQBOLLARI. Экономика и социум, (12-1
(91)), 28-33.

https://academics.uz/index.php/awsit 13
Analysis of world scientific views International Scientific Journal 2024
Vol2 Issue 1 IF(Impact Factor)8.2 / 2023
7. Абдуллажонов, Д. Ш., & Одилов, А. (2023). ОСНОВЫ
ВЗАИМОДЕЙСТВИЯ PHP И БД. Results of National Scientific Research
International Journal, 2(11), 229-241.
8. Shokirjon o‘g‘li, A. D., & SHerqo’ziyevna, T. M. (2023).
KOMPYUTERNING MANTIQIY ISHLASH PRINSIPI. QO ‘QON
UNIVERSITETI XABARNOMASI, 1268-1269.
9. Olimov, I. (2023). DEVELOPMENT OF ARTIFICIAL INTELLIGENCE
IN OUR COUNTRY ALONG WITH INTERNET TECHNOLOGY
INNOVATIONS. Modern Scientific Research International Scientific
Journal, 1(2), 210-216.
10. Surayyoxon, M., & Davronjon, A. (2023). BUGUNGI KUNDA
TALIMDA RAQAMLI TEXNOLOGIYALARNING AFZALLIKLARI VA
KAMCHILIKLARI. QO ‘QON UNIVERSITETI XABARNOMASI, 1210-1212.
11. Mulaydinov, F. M., & qizi Qosimova, G. Q. (2022). QISHLOQ
XOJALIGIDA MEXNAT BALANSI VA UNING MEXNAT RESURSLARIDAN
UNUMLI FOYDALANISHDAGI ROLI. Results of National Scientific Research
International Journal, 1(9), 587-592.

https://academics.uz/index.php/awsit 14