[go: up one dir, main page]

LWC

Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 2

Salesforce has been on a fantastic journey with Lightning components.

Years ago,
Salesforce developers were using a unique HTML tag-based Mark-up language known as
Visual force pages and Apex as their controller for logic.

In 2014, Salesforce launched the Lightning Component framework supported by the


Aura programming framework. Since the web standards offered limited feasibility to
build large-scale web applications at the time, Aura came with its component-driven
model that allowed developers to build large-scale client applications on the web.

Fast-forward to 5 years from the time of Aura; the web stack has seen an
unprecedented level of innovation and standardization that transformed it from
being a rudimentary page-rendering platform to a web development platform.
Lightning Web Components: An Introduction

Lightning Web Components (LWC) is a stack of modern lightweight frameworks built on


the latest web standards. It is a DOM (Document Object Model), element created
through reusable code and is used to generate a dynamic interface without using
JavaScript or building a Library. This feasibility makes it quick and seamless,
saving the developers a ton of time and effort on the Web Stack. Let’s look at some
of its remarkable features:

Improved performance of the component as most of the code is recognized by the


native web browser engine and web stack
Ability to compose applications using smaller chunks of code since the crucial
elements that are required to create a component is part of the native web browser
engine and web stack
Increase in the robustness of the applications built using LWCs as they are
inclusive of the said modern web standards.
Parallel interoperability and feasibility to use both Lightning Web Components
and Aura components together in the applications with no visible differentiation to
the end-users

If LWCs get the same UI result, what is in store for Web Stack?

Languages like React, Angular and the Lightning Components Framework which use
JavaScript are now part of the modern Web Stack. Consequently, the Web Stack no
longer requires an additional mid-layer which used to be a challenge for the
developers working with Aura as it impacted the speed and performance of the
applications.

web stack transformation

The addition of above features give more power to our web Stack to create a
lightning UI component, It doesn’t require a mid-Layer to the browser which impacts
our speed and performance. This one is the main reason developers are struggling
within Aura and now LWC will work for them.
Aura-based Lightning components are built using both HTML and JavaScript,
but LWC is built directly on the Web stack.
Web components can easily interact with the Aura component and can handle
the events of one another
A developer who works on LWC is not only using coding skills on a
particular framework but in other frameworks like React or Angular, which are based
on the Web Stack.
In addition to the latest features, LWC still embraces the features like
the Security, Lightning Data Service, and Base lightning components from Aura.
Creating an LWC is fast as it no longer requires the user to download the
JavaScript and wait for the engine to compile it before rendering the component.
It is possible to include LWC in Aura, but not the other way around as the
generic elements cannot be added to the custom components.
lightening components
Next Best Action

If your organization is already using Aura-based lightning components and the


development team is highly skilled with the Aura framework, here’s the good news —
the Aura Framework is not going anywhere. However, LWCs are the future of lightning
development.

For the most part, if you are building new functionality consider using LWCs to
benefit from the increased native operation in the browser and performance. Just
starting? LWCs are the future.

You might also like