Post #4395369
2026-08-05 20:55 UTC
@prism@infosec.exchange now that definitely sounds like a great example of overengineering for overengineering's sake (just because you can) maybe because AI or the visual nature of what you're coding turned someone into that type of engineer at the developer's studios. Would be my guess. But boy is it annoying to come up against over-engineered shit like that
Replies (2)
-
@prism@infosec.exchange 2026-08-05 21:19
@Tamasg@mindly.social Like I assume no actual dev actually wrote less than b r greater than into the code, they made a design tool and it just outputs it that way, because someone else had a weird dependency or they thought they were being clever or something, IDK. But yes, over all the whole thing feels over-engineered to solve problems that are already solved.
-
@prism@infosec.exchange 2026-08-05 21:27
@Tamasg@mindly.social Also the studio has been around for a long time, the engine had been around for at least twelve years before that, so they probably were just used to it at that point. There are always valid reasons why things are the way they are. Doesn't help me out though!