>OOP is great for GUIs, it's actually the bestIs this actually the case though? Or are we just mistaking the natural mapping of OOP onto the logic of our naive mental frameworks?I don't think I've ever seen a UI paradigm that even attempted doing something that's not OOP or a similar imperative approach.
>>107262633You're coping hard, OP. OOP does map nicely to widget hierarchies and event handling because GUIs are inherently stateful and compositional—buttons have properties, containers hold children, etc. But it's not the only game in town, and claiming it's "the best" is peak Stockholm syndrome from decades of Smalltalk/Windows hegemony.There are plenty of non-OOP paradigms that work just fine, or even better for certain use cases:>Declarative/Functional UIs**: Think React (with hooks/functional components), Elm, or Flutter. You don't mutate objects imperatively; you declare what the UI should look like based on state, and the framework diffs/reconciles changes. No "class Button extends Widget" boilerplate—just pure functions mapping data to UI trees. Elm in particular is purely functional, no side effects, and it's great for web UIs without the OOP cruft.>Immediate Mode GUIs**: Libraries like Dear ImGui or Nuklear ditch the retained object model entirely. Every frame, you procedurally describe the UI in code (e.g., if (imgui.Button("Click me")) { do_stuff(); }). No persistent objects, no inheritance hierarchies—just functions calling functions. Super lightweight for games/tools, and it avoids the memory/state management hell of OOP GUIs.- **Data-Oriented/ECS Approaches**: In game engines like Unity (with newer DOTS) or Bevy, UI can be treated as entities with components, not objects. It's more about data transformation than method calls on instances.We've stuck with OOP for GUIs mostly because early frameworks (MFC, Swing, GTK+) were built that way, and it mirrors how we think about physical interfaces (e.g., "this window owns these buttons"). But if you look at modern web dev or mobile, declarative is eating OOP's lunch for productivity and maintainability. Try building something in Svelte or SolidJS—feels liberating without the class bloat.
>>107262701Fuck off LLMfag>>107262633Fuck off tranime whore poster
>>107262724Based. You tell them.>inb4 Fuck off ass kisser
>>107262701Every programming paradigm has state. The fact that GUIs are compositional would imply OOP is a poor choice since it expresses and handles composition rather poorly. None of your examples are really foundationally different from any each other.
