Most likely the difference in performance is due to differences in expectations. The two greatest common failures I see repeated among software developers is:
1) The inability to consider diverse perspectives
2) The inability to differentiate writing instructions from building something larger
For example many developers cannot imagine the career requirements associated with other careers. That could be due to lack of experience diversity, poor empathy, or weak imagination.
Likewise, many developers cannot write original software. The very idea is frequently both horrifying and disgusting. The alternative is just a little help from a tool or framework, because they write instructions not applications. The interesting part of that is how people respond when confronted about it.
I have seen developers confused by the words writing instructions before, suggesting either they do not know what writing is, what instructions are, or that they cannot differentiate between writing an application and writing a few instructions.
Not OP, but I infer that "writing instructions" equates to a lot of basic scripting - change the colour of that button, show a calendar, trigger that animation, send data to the validation script and display an X or a tick depending. As differentiated from, or opposed to, writing complex applications that require thought, design and awareness of best practice.
* You can write superior applications in JavaScript by not using a framework. By superior I mean more maintainable code, spend less time writing code, execute faster.
* The DOM is most clearly understood when compared to file systems.
* You can do absolutely everything in the browser 8x faster by substituting web sockets for HTTP
Leet code is like prostitution. It’s cheap, short term, and the employment prospects are high risk / low reward.
In most of software there is no relation between being a good developer and being either highly valued or highly employable. Being good requires lots of practice solving tough problems. Being highly employable means high familiarity doing average things with tools incapable of solving tough problems.
Still nothing compared to the billions so many VCs have lost on crypto this year ignoring those far more obvious red flags. No matter how bad Elon damages Twitter at the very least its actually still generating revenue. I cannot tell what crypto generated.
VCs made plenty of money, they receive pre-mined amounts of whatever token they're investing in, and then dump it on retail once the coin lists on the exchanges.
> When data proved his idea was wrong, he would say words to the effect of "I don't care, because I still believe I'm right from an ideological background".
I cannot imagine commercial software in any form where that is not the prevailing sentiment. I have heard of developers who actually measure things in the capacity of their corporate employment but in 20 years of doing this work I have only seen it once.
As such I don’t even bother mentioning performance or correctness at work (across all my employers) where evidence is so hastily discarded and inconvenient conclusions are a suicide pill.
What is freedom of speech? Does the freedom to say what you will qualify theft, violations of privacy, and other illegalities? There is no confusion between the freedom of expression and the harms therein. The freedom to express applies to future conduct where the resultant harms are events that actually occur (past tense). People advocating for Assange seem challenged to this distinction.
* Transmission - I am using HTTP to request assets into the page, I have managed to reduce my total asset requests down to only 4. Other than that I am using websockets for absolutely everything, because the way I am using websockets is 8x faster than HTTP. Its like all the benefits of gRPC without the frustration of protobuf. It isn't just faster its also way easier to manage from the application code because there is no round trip and no callback/promise/await on transmission. Just fire and forget.
* Automation - I am automating the shit out of it. I am automating my documentation, bundling, compilation, and a few other things as much as possible in my build step, which is under 4 seconds. I use TypeScript to type absolutely every declaration. I use TypeScript-ESLint to enforce use of TypeScript declarations and a bunch of custom rules to eliminate known bad practices like "this", bind, call, and apply.
* Framework - What a dirty word. I am not using any of this nonsense. TypeScript is good enough. I have a simple 4 step solution for state management, otherwise I just work directly to the DOM and my current application is an OS GUI. Don't knock it til you try it.
* Performance - You don't know how slow you are until you measure things with numbers. Today I managed to reduce my page load time with state restoration (an OS GUI in the browser) from about 300ms to 192ms by eliminating a CSS reflow and removing 90%+ instances of innerHTML. In the browser the performance tab/graph in the developer tools is fantastic. In Node I prefer to write my own performance tools that typically intertwine with test automation. I eliminated the css reflow by visually hiding all dynamically rendered elements until everything is fully built into the DOM. To dynamically size things vertically I removed some JavaScript arithmetic based upon parent container clientHeight and instead am using CSS min-height:100%.
1) The inability to consider diverse perspectives
2) The inability to differentiate writing instructions from building something larger
For example many developers cannot imagine the career requirements associated with other careers. That could be due to lack of experience diversity, poor empathy, or weak imagination.
Likewise, many developers cannot write original software. The very idea is frequently both horrifying and disgusting. The alternative is just a little help from a tool or framework, because they write instructions not applications. The interesting part of that is how people respond when confronted about it.