How promising is XAML?

Question

Programming languages

I am learning C# WPF. Accordingly, I want to write beautiful applications, in terms of design.
C# uses XAML for this.
Having experience in HTML, CSS, Javascript and other web, I have a lot of questions.
Why reinvent the wheel when everything is already there?
Why complicate things? Why take a step back in terms of incomprehensible grids, nesting, etc.
Grids are reminiscent of the outdated tabular layout model.

That is, on the one hand, the XAML developers did everything in their own way, despite the fact that there is already a model / syntax / logic of HTML / CSS / Javascript that has been worked out for decades - I don’t want to copy.
On the other hand, many things have been complicated.

Also disappointing is the lack of a normal visual editor. Not only XAML, QML too, etc.
The editor in VS is reduced to a kind of browser with the ability to drag and drop elements and change their base values.

How promising is XAML?

Answer 1

So do you want to write beautiful applications or talk about the future of XAML? If you don't like what's stopping you from continuing to write in html, css, javascript

Why take a step back in terms of incomprehensible grids, nesting, etc.

Html is just a bunch of nesting, just like any XML-like language. The grids are very clear, maybe you haven’t figured them out yet, get used to them over time. But html is not such a convenient thing, there people had to invent bootstrap to have grids, but here everything is already at the language level. Yes, grid was recently added to html, when there are already millions of sites using bootstrap, well, better late than never.

model/syntax/logic HTML/CSS/Javascript

What?
Are you going to program in C# or what? Why do you need slow-witted javascript, yes it’s easy and convenient, I also really like it, but because of the support for old browsers, it pulls a huge baggage of shit, well, again, what does javascript have to do with it?
CSS yes, styling on the web is much more convenient than on XAML, but on XAML it is more flexible and specific, with all sorts of multi-triggers and other features, which is not even close to CSS.

Also disappointing is the lack of a normal visual editor. Not only XAML, QML too, etc. The editor in VS is reduced to a kind of browser with the ability to drag and drop elements and change their base values.

Well, I hope you do not create elements by pulling them from the toolbar? Yes, sometimes it is buggy when creating complex styles, reloading the tab and norms. But we see our interface in real time, so that this happens when layout on html, you usually need to resort to third-party plugins for the editor on which we write, and here everything is out of the box.
Perhaps if you started with XAML and programmed for a long time on it, and then switched to html / js / css, you would say why all this if there is XAML.
Krch speaking speaking these are 2 different technologies working by different principles, it is not necessary to put everything under one brush. Html/js/css is far from the ideal that everyone should strive for.

Answer 2

on the one hand, the XAML developers did everything in their own way, despite the fact that there is already a model / syntax / logic of HTML / CSS / Javascript that has been worked out for decades - I don’t want to copy.
On the other hand, many things have been complicated.

This language, like c# , was developed by Microsoft , so perhaps the goal was to create your own language, and not copy an existing one.

Answer 3

XALM is a highly specialized project. In my opinion, the big projects that are written on it were written at the time of the hype around it. Now I would not start a new project on it.