> just as nobody wants to type opcodes, or write their own http clients
This is how you get faster software. You literally look “into” the code, see why stuff is slow, remove the extra work in the library that you do not need, and now your software has a faster server.
Abstractions make software “easy” to build. We’re not looking for done easily, we’re looking for done well.
There are plenty of people who understand the stack and ship actually fast software. This might be a skill issue that you’re choosing to frame as a “best practice”, because you do not want to put in the work.
Our end users are who should benefit. You’re the pilot in the seat who doesn’t know what the throttle is and you’re telling the passenger it’s the plane’s fault it’s slow.
Abstractions are convenience. They’re not free, there is a cost to any work you ask the computer to do. Just staying at the surface level and never understanding what’s under the top level is why software is slow and bloated today. You’re supposed to move beyond the abstraction, understand what you need underneath and use what you really want to do the task.
No wonder we boot up entire browser engines to write simple text editors. But hey, we gotta be first to market to get that VC money, right?
I’m certain there’s enough actual game engine code in the datasets that with enough token spend, you could have a platform layer, basic renderer, entities moving around.
There would be absolutely no point in creating one over using one that exists and since there’s no learning that’ll come of it, it’s kinda wasting money.
This is how you get faster software. You literally look “into” the code, see why stuff is slow, remove the extra work in the library that you do not need, and now your software has a faster server.
Abstractions make software “easy” to build. We’re not looking for done easily, we’re looking for done well.