>>50I know how to optimize shit. And I know that optimization in general includes massive technical lock-in and prevents future modification, as well as assumes today's optimization tradeoffs when tomorrow's will change.
Speed optimization also almost always requires more hardware, for parallelization, caching, precalculation, analytics, and performance heuristics. That's the shit that makes things run fast, not some Cudderfag dicking around with deciding which asm instruction to best traverse an array. You want things running dramatically faster, it's an architectural fact that you will end up throwing much more hardware and software footprint at it as well.