Do you prefer to use UI frameworks which make a distinction between UI files and application code (e.g. Qt, GTK, Angular) or do you prefer to define the UI in the application code (e.g. Flutter, Jetpack Compose, React)?
Do you prefer to use UI frameworks which make a distinction between UI files and application code (e.g. Qt, GTK, Angular) or do you prefer to define the UI in the application code (e.g. Flutter, Jetpack Compose, React)?
4 Comments
Lmaydev@programming.dev · 5 pts · 3y
Always separate where possible. In my experience things can end up a tangled mess really easily.
I'm a big fan of mvvm. Keeps everything separate and simple.
nargacu83@lemmy.world · 3 pts · 3y
nachtigall@feddit.de · 2 pts · 3y
I prefer to define the UI in application code, because separation introduces a lot of overhead for bindings.
Nevertheless, I think it is important separate UI code from business logic.
glibg10b@lemmy.ml · 1 pts · 3y
Separating them allows you to add additional interfaces, such as command-line interfaces, APIs and web pages
fusio@lemmy.world · 1 pts · 3y
depends what you mean by application code.. I'd say if your business logic is exclusively used by a ui feature the best is to keep them together. but you probably want to abstract away things like data access. I found working with a nx monorepo helps reasoning about how to structure your code.