Theoretically, yes, in practice, no.

excellent, i dont need it to think, i need it to execute.

Turns out building houses is super profitable once you remove the cost of building materials, labor, and land.

Ok, but a more honest comparison here would be removing the cost of hiring architects and hiring lawyers to draft contracts, not all the per-house costs.

> removing the cost of hiring architects and hiring lawyers to draft contracts

For multi-unit houses, sure. The actual analogy is closer to removing the cost of the cement plant from every house. Fixed versus variable costs.

from people without ad blockers, but honestly facebook is not the free open internet.

in theory, no, in practice, yes.

By "in practice" do you mean with one-implementation languages?

If there's more than one implementation, there better be a standard, and it's risky to assume any behavior not specified in the standard will be shared by all implementations.

Even with one-implementation languages it becomes risky to assume behaviors will remain the same as the implementation evolves.

i mean the whole ecosystem, compiler, CPU, etc. I think that the compiler will produce performant code, and i think that the CPU will execute code that operates a certain way faster, and that its pretty safe to assume this.

Basically, I think that in 10 years, in practice, radix sort will still be faster than quicksort, despite theory saying its slower.

Theory says radix sort on a set of strings runs in time linear in the sum of the sizes of the strings.

if you use the linux kernel that amount of ram is tunable, and write will cause backpressure on its own when this is exceeded.

limited resources, no modern GPUs, no $10 billion dev budgets.

pair it with codewhale, 50 agents, 200 MB of ram.

CPUs aren't black boxes. They are actually much better documented than almost all the software that runs on them.

If you want to treat the CPU as a black box, trust me you do not want to use a CPU with out a branch predictor, your slow code will run like molasses frozen in antarctica.

The regular algo will be lightyears slower on any CPU that does not have a branch predictor.

yes, but the unstated caveats for fastest are

"i can't program, i only make CRUD apps"

"i don't write anything that requires computation"

"i do server side rendering on a serverless platform"

in reality rails runs circles around typescript for productivity for CRUD/webapps.

haven't web browsers always been C/C++? they are typescript now? it would seem the fastest way to support Mac, Windows and Linux is 500MB of C++.