3 ms·
I've been building gui applications for the past 20 years and I couldn't imagine doing it without an inheritance model. There's so much scaffolding needed to bu
by seanalltogether 11mo ago
I've been building gui applications for the past 20 years and I couldn't imagine doing it without an inheritance model. There's so much scaffolding needed to build components and combine them into a working view. Sure inheritance can be bad in the data layer because you don't want to handcuff yourself to bad data expectations. But building out views and view controllers, there's a lot of logic you don't want to keep duplicating every time.
- kragen 11mo agoGuess what, lots of people have been building GUI applications without views, much less view controllers, for longer than that. Including Squeak, with Morphic.
- simplesocieties 11mo agoAnd yet somehow the Zed team managed to do it with gpui and rust.
- seanalltogether 11mo agohttps://github.com/zed-industries/zed/blob/main/crates/gpui/examples/input.rs https://github.com/zed-industries/zed/blob/main/crates/gpui/... GPUI is a great example of the insane amount of boilerplate needed to create a component when you don't have inheritance. My guess is that people don't create a lot of individual components in this framework to handle different business cases, and instead overload a single text input component with a million different options. I would hate to untangle a mature app written under those conditions.