Conversation
Edited 5 months ago

I really wish documentation for opinionated frameworks/libraries would explain what problem they’re trying to solve with their abstractions

instead of just being like “first you create a blueprint, and then you register the blueprint with the dataclasses, and then the dataclasses are inserted into the render engine alongside the server entities, and then the render engine creates an entity-dataclass hybrid mechazord which is shoved into the internet tubes, which…” and I’m just sitting there like “why the fuck do I have to do all these steps in order to [do an extremely basic thing]”

like I’m sure that there is a Very Good Reason but I would like to know what that is because out of context this type of stuff looks like a massively overengineered nightmare for no reason

0
2
6