function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Nik MilaserdovNik Milaserdov 

VisualForce vs Lightning

1) What do you think, when Salesforce completely (or almost completely) abandons VisualForce and switches to Lightning?
2) And why do you think that you should not switch from VisualForce to Lightning?
Alain CabonAlain Cabon

1) There are around 15 billions of existing VFP currently so Salesforce will keep this technology alive for many years. The switch is needed because of the very low governor limits for the VFP and the very restricted standard templates for the pages themselves (much more flexible and adaptable in Lightning, components).

2)  For many end users, the existing Visualforce page are often sufficient but the main problems are not "visible" and are the governor limits of these Visualforce page (pagination always mandatory, first/next/previous/last page) because you have just 170 ko available ( Maximum view state size in a Visualforce page ). Many developers struggle and suffer a lot because of this very low limit. 
(1000 = Maximum collection items that can be iterated in an iteration component such as <apex:pageBlockTable> and <apex:repeat>)

In Lightning, you can have directly the infinite loading for example for a data table (the equivalent of <apex:pageBlockTable> for VFP)

Lex data table = enableInfiniteLoading = boolean - global : Enables or disables infinite loading. The default is false.