Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
pie-flavor3672dNon-trivial GUI-generating code can't be previewed in a GUI editor without emulating the entire environment. Styling also gets harder, and some concepts don't translate well into code (e.g. Grid.Column in XAML). Finally, retained GUI code should nearly always follow a MVC or MVVM pattern to keep logic separate from visuals, and a language barrier is one more way to do that.
inaba461072dI love using markup languages in gui because it makes it easier to order things around. Also in case of HTML there's all these semantic tags which are great for knowing what is supposed to be what
Fast-Nop1277572dProgrammatically? Well yeah, for desktop applications. But on the web, that would mean generating the entire DOM via JS. That leads to issues with performance, SEO and accessibility.
thatsnotnice71772din general, i favour declarative languages, markups & co.
i'm no expert of GUI development in desktop environments, but as for web dev markups are quite a good tool
and as for web, unless you develop for intranet or you use a good server-side rendering system, normally you want standard-compliant HTML on top of everything
AlgoRythm3763472dIn the case of XAML, it makes things more modular. There's less code and less room to fuck up.
Others that come to mind like Quick QT, I think it's called, are useful in their own right. Writing out code to generate your layout is not only time expensive and difficult to read, but whenever I do it, I tend to make more mistakes than if I were using a markup language. And it's more difficult to modify too.
Plus some markup languages give you state modifiers like :hover so you don't need to write event listeners.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job