Sign into an existing account

Speed aside, let's talk about storage/memory size. Every fucking piece of software these days takes 70 fucking gigs of space up. Why? Because lazy motherfuckers use one or two resources from pre-written library and they leave ALL of the pre-written library in place so they don't have to prune for efficiency.

I saw someone's Xbox updating a video game the other day, and my jaw dropped in disbelief when I saw the update was 170 gigs. Are you fucking kidding me? That's 8,500 IBM PC's.

And you have to wonder just how much of the slowdown is from diversity hires copying stack exchange for their enterprise software, and/or the various backdoor programs/algos working in the background to watch/record everything you do.

Not to mention intentional slowdowns for various reasons that then get mindlessly copied endlessly by dot niggers.

While I don't doubt that there is some validity to this, but this is really not why modern code is slow.

Story time:
About 20 years ago I was working as a Software Developer and as my company were part of the Microsoft partner's network we received free tickets to a 2-day workshop on there brand new thing that they said would change software development forever... They were calling it ".NET". So one of my coworkers and I traveled to this event and spent 3 days in a conference hall with 20 other developers from around the country and they gave us a crash course in .NET application development.

As a developer my thoughts on .NET were mixed. It was SUPER easy to use. Nearly everything could be done dragging and dropping objects and modifying parameters in the UI. It was easy... This was Microsoft making software development accessible to people who were not really software developers. Front-end UI engineer could suddenly be productive on the back end. A script kiddie could suddenly make a real application.

And it preformed like shit. I made a hello world app that was a single .NET form with a few text labels and a text field that populated with the string "Hello World!" and when I ran it it took 20MB of memory. Even in the early '00s that was not a lot of memory, but this app was doing literally nothing. It was clear that the .NET framework was an absolute performance pig.

Several of us challenged the Microsoft instructors on this. Their response? "Yeah we know it performs poorly compared to nice tight hand-written code... This is the price you pay for making it so easy to develop in the framework. And we have decided that performance is literally our last concern. Every year CPUs double in speed. Our philosophy is that we are writing the development tools for the next 10 years. What looks like a 'performance hog' today will be just a drop in the bucket tomorrow."

So there you have it folks. Microsoft lead the way but the entire industry followed. Modern software performs so slowly because software developers stopped caring once computers became fast. Software developers prioritized things that make their lives easier.

It’s because most programmers cannot program.

Yeah well when you go to optimize you make it more complicated and manage resources more carefully. I think a lot of the issue is just that people never get there. They're always making the latest widget work, and CPUs are always coming up with more cycles to waste.

There are videos that explain this better in less time. The answer is bloated coding. This shit got bad because of increases in readily available storage. There's no reason to code efficiently and save space on storage devices anymore. If you look to the past, C, the most efficient coding language, was invented to save space and as a result made coding super efficient. If you compare it to languages that are used today which are largely object oriented, it becomes a mess. It gets even worse when you realize most "coders" these days actually just use frameworks to do half the work for them. Which stacks bloat and inefficient coding on top of bloat and inefficient coding.

An interesting comparison study here is SQLite, where any connector/driver has to implement the entire SQLite engine.

Naturally there are some major performance differences depending on platform and query used. Trying to use a Group By when you have a bunch of CTEs (the With clause) and over 9000 Joins can take a full minute with some production implementations, but half a second with the official non-production CLI.

The difference in time between a cache hit and a ram hit is x30.
If you don't know how to optimize your pages, then go hang yourself, faggot!

He's idiotic, though. Most code doesn't matter for performance. Time is spent in loops. What matters more is having a clear picture of the system and being able to configure it to not do unnecessary things. Might as well suggest writing everything in assembler. Except that will make the code slower because you lose flexibility and clarity in the sea of details.

But I think the real bloat and slowness comes from outside, having to use overly-general frameworks to interoperate with other software. These dictate the form of things and have so many layers in each one it's mind-numbing. Feature-creep is everywhere.

there is no clean code.

Necessity is the father of invention.

Creating code that actually does anything efficiently is moot when your average idiot buys a 32 core processor because they need GoyFlix to run along with 300 other apps for shit they never use.