I am a vb.net developer principally, but have done a fair bit of c# work.
I always work in an option strict environment to reduce the unhandled exception risk. This means that all objects are strongly typed and there is no late binding. It has distinct performance advantages.
Now, nopCommerce uses c#, which by default is option strict, allowing no implicit datatype conversions etc.
But I notice in the code that there is a heavy use of variants and dynamic objects, which avoids the usual c# strictness. What is the impact of this on performance?
Also, there seems to be a shortage of stored procedures, with all the data (virtually) selected within the asp. Is this wise? Would not the heavy data calls be better off being processed within the database?
There is a lot here, and everywhere, about nop commerce being a slow application, but it's architecture makes it very desirable. What are the plans within the nopCommerce team to spend some time working on performance?
kind regards