Why Lightning Web Component












1














Why Salesforce has introduced new feature called Lightning Web Component (LWC)? What is the benefit over Lightning Component?



I have went through various blogs to find out the actual need of LWC over Lightning Component. Is it something doing same thing in new way?










share|improve this question




















  • 1




    Christophe Coenrats' introductory blog post is pretty explicit on the benefits. Standards compliance, performance, interoperability, and so forth. Is there a specific aspect you're seeking more detail on?
    – David Reed
    45 mins ago








  • 2




    Possible duplicate of Lightning Web Components - Benefits and Support
    – codeyinthecloud
    42 mins ago






  • 1




    @codeyinthecloud Hahaha, I thought this looked familiar.
    – sfdcfox
    36 mins ago










  • @sfdcfox I remembered your answer on the other one the moment I saw this!
    – codeyinthecloud
    9 mins ago
















1














Why Salesforce has introduced new feature called Lightning Web Component (LWC)? What is the benefit over Lightning Component?



I have went through various blogs to find out the actual need of LWC over Lightning Component. Is it something doing same thing in new way?










share|improve this question




















  • 1




    Christophe Coenrats' introductory blog post is pretty explicit on the benefits. Standards compliance, performance, interoperability, and so forth. Is there a specific aspect you're seeking more detail on?
    – David Reed
    45 mins ago








  • 2




    Possible duplicate of Lightning Web Components - Benefits and Support
    – codeyinthecloud
    42 mins ago






  • 1




    @codeyinthecloud Hahaha, I thought this looked familiar.
    – sfdcfox
    36 mins ago










  • @sfdcfox I remembered your answer on the other one the moment I saw this!
    – codeyinthecloud
    9 mins ago














1












1








1







Why Salesforce has introduced new feature called Lightning Web Component (LWC)? What is the benefit over Lightning Component?



I have went through various blogs to find out the actual need of LWC over Lightning Component. Is it something doing same thing in new way?










share|improve this question















Why Salesforce has introduced new feature called Lightning Web Component (LWC)? What is the benefit over Lightning Component?



I have went through various blogs to find out the actual need of LWC over Lightning Component. Is it something doing same thing in new way?







lightning-web-components






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 48 mins ago









David Reed

29.4k61746




29.4k61746










asked 58 mins ago









Avijit

282414




282414








  • 1




    Christophe Coenrats' introductory blog post is pretty explicit on the benefits. Standards compliance, performance, interoperability, and so forth. Is there a specific aspect you're seeking more detail on?
    – David Reed
    45 mins ago








  • 2




    Possible duplicate of Lightning Web Components - Benefits and Support
    – codeyinthecloud
    42 mins ago






  • 1




    @codeyinthecloud Hahaha, I thought this looked familiar.
    – sfdcfox
    36 mins ago










  • @sfdcfox I remembered your answer on the other one the moment I saw this!
    – codeyinthecloud
    9 mins ago














  • 1




    Christophe Coenrats' introductory blog post is pretty explicit on the benefits. Standards compliance, performance, interoperability, and so forth. Is there a specific aspect you're seeking more detail on?
    – David Reed
    45 mins ago








  • 2




    Possible duplicate of Lightning Web Components - Benefits and Support
    – codeyinthecloud
    42 mins ago






  • 1




    @codeyinthecloud Hahaha, I thought this looked familiar.
    – sfdcfox
    36 mins ago










  • @sfdcfox I remembered your answer on the other one the moment I saw this!
    – codeyinthecloud
    9 mins ago








1




1




Christophe Coenrats' introductory blog post is pretty explicit on the benefits. Standards compliance, performance, interoperability, and so forth. Is there a specific aspect you're seeking more detail on?
– David Reed
45 mins ago






Christophe Coenrats' introductory blog post is pretty explicit on the benefits. Standards compliance, performance, interoperability, and so forth. Is there a specific aspect you're seeking more detail on?
– David Reed
45 mins ago






2




2




Possible duplicate of Lightning Web Components - Benefits and Support
– codeyinthecloud
42 mins ago




Possible duplicate of Lightning Web Components - Benefits and Support
– codeyinthecloud
42 mins ago




1




1




@codeyinthecloud Hahaha, I thought this looked familiar.
– sfdcfox
36 mins ago




@codeyinthecloud Hahaha, I thought this looked familiar.
– sfdcfox
36 mins ago












@sfdcfox I remembered your answer on the other one the moment I saw this!
– codeyinthecloud
9 mins ago




@sfdcfox I remembered your answer on the other one the moment I saw this!
– codeyinthecloud
9 mins ago










1 Answer
1






active

oldest

votes


















3














LWC is meant to be a Lightning Components 2.0. It has a lot of pretty nice features.



Knowledge Domain



Developers familiar with Web Components are mostly familiar with LWC out-of-the-box. Aura is proprietary, so the more you know about web standards, the more you'll have of a skill that can be used outside Salesforce, too!



Better Execution



LWC leverages built-in browser security features from WC standards, so there's less custom code. This means they run faster and are more consistent in how they enforce security. Also, events have a more limited scope, so there's much less processing required to handle events.



New Security Features



We get better CSS isolation, script isolation, DOM isolation, and a more limited event scope, all of which leads to more consistent component design.



ES6+



We now have better support for ES6 and ES7, not available in Aura. You can do more in less code. It also transpiles code to work with IE 11 and other browsers that are missing some features.



More Consistent Data Binding



Two-way data binding, which has always been kind of buggy in Aura, is gone. This forces developers to coordinate how data moves between components. This also means that data binding will work as expected, without the "gotchas" from Aura.



Service Components



You can now write components that have no UI. They simply provide reusable methods that you can use in other components. This is much more efficient than Static Resources.



Mixins



You can import accessible methods from other components (as per above), and also import specific Apex methods, even from multiple classes. In addition, the Apex methods can be cached for improved performance.





Basically, LWC was a way for salesforce.com to fix all the things that were "not quite right" about Aura, while also moving towards web standards. There's no imperative to switch, as both style components are largely compatible with each other, although there's some restrictions to where and how they can be used.



Your Aura skills won't be lost, and you will keep using them (LWC isn't supported in a lot of ways that ISVs and Developers want), but the widgets and so on that make up your Aura components can benefit from using LWC, in terms of performance and security enhancements.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "459"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f244594%2fwhy-lightning-web-component%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    LWC is meant to be a Lightning Components 2.0. It has a lot of pretty nice features.



    Knowledge Domain



    Developers familiar with Web Components are mostly familiar with LWC out-of-the-box. Aura is proprietary, so the more you know about web standards, the more you'll have of a skill that can be used outside Salesforce, too!



    Better Execution



    LWC leverages built-in browser security features from WC standards, so there's less custom code. This means they run faster and are more consistent in how they enforce security. Also, events have a more limited scope, so there's much less processing required to handle events.



    New Security Features



    We get better CSS isolation, script isolation, DOM isolation, and a more limited event scope, all of which leads to more consistent component design.



    ES6+



    We now have better support for ES6 and ES7, not available in Aura. You can do more in less code. It also transpiles code to work with IE 11 and other browsers that are missing some features.



    More Consistent Data Binding



    Two-way data binding, which has always been kind of buggy in Aura, is gone. This forces developers to coordinate how data moves between components. This also means that data binding will work as expected, without the "gotchas" from Aura.



    Service Components



    You can now write components that have no UI. They simply provide reusable methods that you can use in other components. This is much more efficient than Static Resources.



    Mixins



    You can import accessible methods from other components (as per above), and also import specific Apex methods, even from multiple classes. In addition, the Apex methods can be cached for improved performance.





    Basically, LWC was a way for salesforce.com to fix all the things that were "not quite right" about Aura, while also moving towards web standards. There's no imperative to switch, as both style components are largely compatible with each other, although there's some restrictions to where and how they can be used.



    Your Aura skills won't be lost, and you will keep using them (LWC isn't supported in a lot of ways that ISVs and Developers want), but the widgets and so on that make up your Aura components can benefit from using LWC, in terms of performance and security enhancements.






    share|improve this answer


























      3














      LWC is meant to be a Lightning Components 2.0. It has a lot of pretty nice features.



      Knowledge Domain



      Developers familiar with Web Components are mostly familiar with LWC out-of-the-box. Aura is proprietary, so the more you know about web standards, the more you'll have of a skill that can be used outside Salesforce, too!



      Better Execution



      LWC leverages built-in browser security features from WC standards, so there's less custom code. This means they run faster and are more consistent in how they enforce security. Also, events have a more limited scope, so there's much less processing required to handle events.



      New Security Features



      We get better CSS isolation, script isolation, DOM isolation, and a more limited event scope, all of which leads to more consistent component design.



      ES6+



      We now have better support for ES6 and ES7, not available in Aura. You can do more in less code. It also transpiles code to work with IE 11 and other browsers that are missing some features.



      More Consistent Data Binding



      Two-way data binding, which has always been kind of buggy in Aura, is gone. This forces developers to coordinate how data moves between components. This also means that data binding will work as expected, without the "gotchas" from Aura.



      Service Components



      You can now write components that have no UI. They simply provide reusable methods that you can use in other components. This is much more efficient than Static Resources.



      Mixins



      You can import accessible methods from other components (as per above), and also import specific Apex methods, even from multiple classes. In addition, the Apex methods can be cached for improved performance.





      Basically, LWC was a way for salesforce.com to fix all the things that were "not quite right" about Aura, while also moving towards web standards. There's no imperative to switch, as both style components are largely compatible with each other, although there's some restrictions to where and how they can be used.



      Your Aura skills won't be lost, and you will keep using them (LWC isn't supported in a lot of ways that ISVs and Developers want), but the widgets and so on that make up your Aura components can benefit from using LWC, in terms of performance and security enhancements.






      share|improve this answer
























        3












        3








        3






        LWC is meant to be a Lightning Components 2.0. It has a lot of pretty nice features.



        Knowledge Domain



        Developers familiar with Web Components are mostly familiar with LWC out-of-the-box. Aura is proprietary, so the more you know about web standards, the more you'll have of a skill that can be used outside Salesforce, too!



        Better Execution



        LWC leverages built-in browser security features from WC standards, so there's less custom code. This means they run faster and are more consistent in how they enforce security. Also, events have a more limited scope, so there's much less processing required to handle events.



        New Security Features



        We get better CSS isolation, script isolation, DOM isolation, and a more limited event scope, all of which leads to more consistent component design.



        ES6+



        We now have better support for ES6 and ES7, not available in Aura. You can do more in less code. It also transpiles code to work with IE 11 and other browsers that are missing some features.



        More Consistent Data Binding



        Two-way data binding, which has always been kind of buggy in Aura, is gone. This forces developers to coordinate how data moves between components. This also means that data binding will work as expected, without the "gotchas" from Aura.



        Service Components



        You can now write components that have no UI. They simply provide reusable methods that you can use in other components. This is much more efficient than Static Resources.



        Mixins



        You can import accessible methods from other components (as per above), and also import specific Apex methods, even from multiple classes. In addition, the Apex methods can be cached for improved performance.





        Basically, LWC was a way for salesforce.com to fix all the things that were "not quite right" about Aura, while also moving towards web standards. There's no imperative to switch, as both style components are largely compatible with each other, although there's some restrictions to where and how they can be used.



        Your Aura skills won't be lost, and you will keep using them (LWC isn't supported in a lot of ways that ISVs and Developers want), but the widgets and so on that make up your Aura components can benefit from using LWC, in terms of performance and security enhancements.






        share|improve this answer












        LWC is meant to be a Lightning Components 2.0. It has a lot of pretty nice features.



        Knowledge Domain



        Developers familiar with Web Components are mostly familiar with LWC out-of-the-box. Aura is proprietary, so the more you know about web standards, the more you'll have of a skill that can be used outside Salesforce, too!



        Better Execution



        LWC leverages built-in browser security features from WC standards, so there's less custom code. This means they run faster and are more consistent in how they enforce security. Also, events have a more limited scope, so there's much less processing required to handle events.



        New Security Features



        We get better CSS isolation, script isolation, DOM isolation, and a more limited event scope, all of which leads to more consistent component design.



        ES6+



        We now have better support for ES6 and ES7, not available in Aura. You can do more in less code. It also transpiles code to work with IE 11 and other browsers that are missing some features.



        More Consistent Data Binding



        Two-way data binding, which has always been kind of buggy in Aura, is gone. This forces developers to coordinate how data moves between components. This also means that data binding will work as expected, without the "gotchas" from Aura.



        Service Components



        You can now write components that have no UI. They simply provide reusable methods that you can use in other components. This is much more efficient than Static Resources.



        Mixins



        You can import accessible methods from other components (as per above), and also import specific Apex methods, even from multiple classes. In addition, the Apex methods can be cached for improved performance.





        Basically, LWC was a way for salesforce.com to fix all the things that were "not quite right" about Aura, while also moving towards web standards. There's no imperative to switch, as both style components are largely compatible with each other, although there's some restrictions to where and how they can be used.



        Your Aura skills won't be lost, and you will keep using them (LWC isn't supported in a lot of ways that ISVs and Developers want), but the widgets and so on that make up your Aura components can benefit from using LWC, in terms of performance and security enhancements.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 36 mins ago









        sfdcfox

        246k11186423




        246k11186423






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Salesforce Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f244594%2fwhy-lightning-web-component%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Calculate evaluation metrics using cross_val_predict sklearn

            Insert data from modal to MySQL (multiple modal on website)