3 ms·
Problem is some CS grad comes along, sees this and thinks "What if that were HTML?" and now we have the current state of front-end development. Sad. All we real
by gabereiser 3y ago
Problem is some CS grad comes along, sees this and thinks "What if that were HTML?" and now we have the current state of front-end development. Sad. All we really want is a const o = new Div("#my-thing"). I remember doing XAML development back in the WPF hay day. 2009-ish. Csaml and Xaml are pretty close. I hated Xaml a lot. So much so that all the views and components I wrote at the company I worked for were done using Canvas + DrawVisuals as to avoid Xaml all together. Funny, sad, ironic, and nostalgic all at the same time.
- fassssst 3y agoYup. SwiftUI does it right. One language for your whole app.
- zerr 3y agoI find Flutter's nested hell quite unpleasant to read or write. For declarative UI, XAML seems like a better approach.
- zigzag312 3y agoJust break the tree into smaller semantic components. I, on the other hand, find XAML much more unpleasant to read or write than Flutter.
- TillE 3y agoA mistake I've made a few times is thinking let's separate code and data, that sounds great. But then I realize I need to do some pretty complex stuff in the data, and I'm faced with the choice of building some hacky monstrosity, or a DSL, or just going back to the main code. The basic tutorial examples of SwiftUI look like something you could easily do in XML, but doing it in real code makes it so much more powerful, and ultimately simpler for everyone.