3 ms·
It is not. macOS/iOS had it for a long time with AppKit, UIKit. But the progression is usually this: you start with Interface Builder and storyboards or .xibs,
by rimliu 3y ago
It is not. macOS/iOS had it for a long time with AppKit, UIKit. But the progression is usually this: you start with Interface Builder and storyboards or .xibs, then you see the problem with that and gradually move to code-only UI and then start looking at SwiftUI with it's declarative UI like a guy in that meme.
GUI for layout just does not cut it, especially when your app runs in very different environments - it can be macOS, it can be a phone or just a smartwatch/widget.
- treprinum 3y agoAlternate take: macOS/Qt/MFC/React etc. got it wrong, Delphi got it right.
- steve1977 3y ago> especially when your app runs in very different environments - it can be macOS, it can be a phone or just a smartwatch/widget. But the question here is also if it makes sense to basically have the same UI or even UI paradigms for such different types of environments.