Hacker News Reader

Comment by nwah1 | Hacker News Reader

Have the exact opposite experience.

The inconsistency of the web platform is a nightmare compared to my pain-free experience with XAML.

XAML and C# allows a single developer to get a functional modern application going quickly.

I had zero problems with extensibility as long as I followed the patterns. Using MVVM, convertors, triggers, events, and behaviors where needed. The Blend tool is ridiculously cool, but I'm not artistic enough to make great use of it. But it reminds me of how Flash made me feel early on. As a kid I could make cartoons without issue in Flash.

Almost everything is open source or has an open source replacement available.

Making new UserControls is trivial. Much easier than any Web Components nonsense.

View on HN

idk, maybe its just because I'm so inexperienced and I was learning this as I go, but it all seemed great to begin with, but quickly fell out once i got into the reality of actually developing and designing.

I still don't know how you're supposed to properly update data for a grouped List/GridView without causing the entire view to rerender. I'm so used to React's functional approach to building UIs that mutating collections seemed extremley alien and cumbersome to me.

I still never found a good way to achieve this a in in XAML, a grid layout where the cells will expand to fill remaining space on the row, and then wrap. Multiple components got kind of close, but always lacked 1 aspect https://codepen.io/joshhunt/full/qBOdYjj

> how you're supposed to properly update data for a grouped List/GridView without causing the entire view to rerender

By telling your views what was updated.

For updating sets of items, see INotifyCollectionChanged interface, implemented by ObservableCollection<T> from the framework.

For updating properties, see INotifyPropertyChanged.

> Multiple components got kind of close, but always lacked 1 aspect

Find a panel that does it best, then either copy-paste and patch, or inherit and override.

The entire layout model is implemented in just 2 methods, MeasureOverride and ArrangeOverride. They are virtual, i.e. designed to be user-replaceable as you inherit from framework classes.

The original complaint was mostly around layout patterns. I'm not super familiar with XAML, but "offloading that all into writing custom C# code to lay things out at pixel locations" certainly doesn't sound like a great dev experience, and definitely doesn't sound very responsive. Does XAML have anything comparable to flexbox/grid for building responsive layouts?

> Does XAML have anything comparable to flexbox/grid

WrapPanel

> for building responsive layouts?

There're two kinds of them. On the web it means arranging stuff to only have vertical scrolling but not horizontal. On desktop you often don't want any scrolling, no amount of auto-wrapping is going to do that regardless on the GUI framework.

Reply on news.ycombinator.com