WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

673

(post is archived)

[–] 8 pts 1y

Obviously. Few programmers understand how to optimize. Worse, because of the idiocy of modern development processes like AGILE, optimization is always placed as a very low priority. That is, unless performance criteria are well defined - which they almost never are.

Of course, language choices like C# and Java have had their own share in destroying performance.

[–] 1 pt 1y

Which do you think is the most likely reason: beta fags who don't push against business, or non-whites? I've seen both having a negative impact on software quality.

[–] 3 pts 1y

Lots of factors at play. BAs/managers/execs are taught optimization is no longer needed because of horizontal scalability. No one ever thinks about where this idiocy originates.

This is combined with "cloud" computing vendors (example, AWS) teaching it's cheaper than owning your own (actually around 20%-30% more, including labor). Which they love because unoptimized apps means more bank for them. Popularity only confirms how unqualified most management actually is for the industry.

Non-whites traditionally mean non-optimized, buggy, poorly documented, poorly designed code. Developers who can optimize are higher end veterans and are harder to come by. So they pool cheap labor and let the brains fix all the bullshit so it's "good enough." In theory saving bank. Which is almost never true because their projects are usually very late and under delivered. Which means at best they broke even with a skilled project which would have been delivered on time. But they still get reduced labor rates as the primary push for non-whites is wage suppression. Want to know what you should be making? It's anywhere from 40%-300% more than you make today. That's the Indian contribution to the tech market.

As for pushing against business, this is the genius of bullshit like AGILE. It shifts the blame onto the developers so they pretend the developers are at fault while hiding the fact that it's still managers and execs causing the problems. "Well, you said you could do it in x." Never mind management set the requirements, almost never provide time for estimate and project analysis, or time for an actual design. "We didn't know about x." "Well, you said you could do x in y time." "You said it had to be done is y time and x is/was unknown as you didn't provide project time." "You have a bad attitude. Developer is difficult with which to work."

Languages like C# and Java came to be specifically because languages like C and C++ are too hard for non-whites. While they love to lie that these provide C and C++ performance, in reality, especially when combined with lacking optimizations, they are commonly 4x-8x slower than a C or C++ equivalent. See first and second points above.

Add to this that BAs and manager/exec idiots are taught that web everything is a good idea, we wind up with environments where many apps run orders of magnitude slower than a native app. Honestly, JS/TS are some of the absolute shittiest languages I've ever had to use. But this tier of developer tends to be second or third so generally don't suffer with them much. The combination is massive overhead on the front end (which they generally don't pay for - except for lost labor waiting) and massive overhead on the backend, for which they now pay a premium.

The result is the overhead and lost time and suppressed wages all create justification for more "out sourcing" and pajeets who further drag the entire industry and economy down.

There's a reason why Space X is highly successful, less expensive, and has almost exclusively white males.

↓ expand content
[–] 1 pt 1y

I wish I'd worked with you instead of the dickheads I've worked with over the past few years. I know I'd have learned a lot. Do you see with any frequency any up-and-comers with whom you do work, who might carry on with a better tradition to contrast the pajeets writings shitty Angular apps?

[–] 5 pts 1y (edited 1y)

I once put windows 95b on a pentium 2(?) and that fucking thing loaded so fast it was bonkers. I could not believe it. By then the os of choice was 98se, me, or 2000. Nobody was looking at 95.

It was like bios screen ....... and then.... tada, done.

[–] [deleted] 4 pts 1y

It's so true, I've had to recently start monitoring memory usage much more closely even on machines with 16+ gigs ram or higher.

Pretty ridiculous.

[–] 3 pts 1y (edited 1y)

Silly Goy, the faster computers are to make (web) developers' lives better, not yours. It's quite a trick they pulled where even if you don't change the software on your machine, web browsing will get painfully slow as the years go on.

[–] 3 pts 1y

By modern they mean "not linux"

[–] 3 pts 1y

A long time ago, there was an editor called Brief (designed by Underware) I loved. It worked great, right until version 3. It slowed way down because they added some new tricks. When I noticed this and talked to the developer, his response was "get a faster computer."

I'm quite the opposite. I design software that runs fast on tiny Raspberry Pis because it's very possible, but it takes knowledge to do. Instead of buying fast hardware with 32 cores and gigahertz CPUs, fast DDR RAM, I buy cheap, ubiquitous commodity hardware.

I will add, part of the problem is hardware cost. People tend to virtualize computers into tiny Docker VMs. Now you've taken that super powerful computer and stressed it so it's running a huge AKS cluster of many small virtual machines.

[–] 3 pts 1y

AVR (which Arduino uses) is pretty fun. 8-bit RISC, tens of K of flash, and still programmable in C with just gcc and avrdude to flash it. Mostly on-the-metal stuff (no room for an OS).

[–] 2 pts 1y

Docker is so light compared to the apps that run inside the containers. It mostly isolates groups of processes from each other, in terms of memory, network, filesystems, etc. but the containers are all running under the same kernel (and thus the same device drivers). Very different from the thick layer that actual virtualization stacks bring like vmware / vbox.

[–] 0 pt 1y

Sure. But when you hundreds or thousands of small containers....

[–] 2 pts 1y

And that's gotten worse with 64-bit's support of near limitless RAM. Add in some Pajeet programming (which is probably cut and paste from random internet forums) and you've got a hellava mess.

[–] 3 pts 1y

Plus, switching from 32-bit to 64-bit also doubles the size of a memory pointer, which significantly grows the memory footprint of most apps in unexpected ways. For example a simple map is implemented as a node tree, each node containing a couple pointers to other nodes. Now every element added to the map needs another 8 bytes of overhead.

[–] 1 pt 1y

Of course. Slopes and pajeets care only about getting it done and making money.

[–] 1 pt 1y

React framework has been the death of performance. Having a web layer between everything is just lazy.