<story><title>Open-sourcing the Lightning Web Components framework</title><url>https://developer.salesforce.com/blogs/2019/05/introducing-lightning-web-components-open-source.html</url></story><parent_chain></parent_chain><comment><author>tvanantwerp</author><text>I (thankfully) don&amp;#x27;t have to use Salesforce very often. But from my experience, the Lightning Experience always felt non-performant compared to the traditional server-rendered pages. Things always took a noticeable amount of time to finish loading. Even though the traditional interface is, by appearance alone, quite traditional, as least it felt fast. I don&amp;#x27;t know if Lightning&amp;#x27;s problems were with poor performing front end code, or poor API performance. But I was always underwhelmed when testing the SPA version of Salesforce.</text></comment>
<story><title>Open-sourcing the Lightning Web Components framework</title><url>https://developer.salesforce.com/blogs/2019/05/introducing-lightning-web-components-open-source.html</url></story><parent_chain></parent_chain><comment><author>miloandmilk</author><text>A lot of Salesforce sites use react - including:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;status.salesforce.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;status.salesforce.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;and ironically:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.lightningdesignsystem.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.lightningdesignsystem.com&amp;#x2F;&lt;/a&gt;&lt;p&gt;Why do they insist on forcing their framework of the week on  their dev community and make it much easier to bring your own framework? NIH syndrome? Lock in?&lt;p&gt;We use react and visualforce to get our products built but the visualforce requirement to do so is sub optimal.</text></comment>