It is difficult to answer the specifics, but not all options that are made in software development are created equal, even using the same language. The more layer on the framework layer you stumble upon something, the further you get away from “what is really important”, and if “what is really important” is productivity, a person who can program at this “lower level” can do a lot , many times faster than people who develop programs by combining controls. Sometimes simplicity of development is more important than speed of raw materials, therefore it is not always the right choice at the lowest level - simplicity of code maintenance is also important and sometimes outweighs raw performance.
Once I went to the head with another consultant trying to win a high contract of 6 pieces for a large financial services firm, we both sold the idea of a BI / EIS system. He used inflated technologies and every step of the way, but all this was a “new and brilliant” technology, on which he was very proud and contained all the right keywords.
I wrote mine in asp (asp classic, .net wasn’t yet) and uses custom written SQL Server native methods of communication with all manual encoded procedures to generate reports and other similar productivity solutions. He used a plug-in for recording reports and plug-and-play controls to create his system. I did my entire demo on switch 28.8 against my development web server in my home office 200 miles away - it was done against a much more powerful development server in the next room, connected via a 100 megabyte ethernet, and there was still a lot. many times slower.
When the demonstration ended, I told my clients that my entire demonstration was done over the telephone line (they assumed it was local). This sealed the deal, as most users of the system were scattered across the country, and broadband was unusual at the time.
source share