XAML components ("controls" in MS terminology) contain both declarative markup and code. And it's flexible because the visual presentation can be completely overriden by the component's consumer without altering behavior, and your code can be either C# or C++.
What does dependency injection have to do with anything? There's nothing stopping you from using global variables or an event bus or something like Redux in a XAML app.
About the same here in Seattle. It makes saving for a down payment even more depressing.
I don't understand who is able to buy these houses when my partner and I can't as software engineer + physician assistant. Maybe it's just because we're not willing to decrease or dip into our retirement savings and we have no help from parents.
I just don't feel comfortable taking out a jumbo mortgage. Even though we could make the numbers work, I'm not confident either of us won't burn out from our stressful careers.
We're on a small rock flying through an infinite universe. Our lives exist in a small blink of time. Computers run billions of operations per second using software with countless defects at every level of the stack.
We're lucky anything works at all. In that context, we succeeded just by being born and living as long as we have, and we'd be pretty narrow-minded to assume that the material success we enjoy is significantly more than a series of happy accidents.
Not sure why you're being downvoted. XAML definitely supports complex widget composition in markup. Since the XML is basically just describing an object graph, it's a more concise way of writing the equivalent imperative code:
One cost of all the guns is all the extra security. Schools resembling prisons, TSA, metal detectors and surveillance everywhere... doesn’t that also infringe on my freedom in a way?
The estate tax is justified as a means of reducing the concentration of wealth. However, the truly wealthy and their estate planners avoid the tax. The low yield of the tax is a testament to the ineffectiveness of the tax as a force for reshaping the distribution of wealth.
Of course, those recommending the repeal of the estate tax are also probably of the opinion that wealth concentration is not a problem.
Apple Watch has a crown and a touch screen. iPad Pros have keyboards, pens, and a touch screen. Apple TV has directional and trackpad input. All support voice input. All work fine with basically the same UI toolkit.
That's an orthogonal problem. Why should the Apple platform arbitrarily require you to use different toolkits for different form factors or input modalities? They already support phones, tablets, TV's, and watches with the iOS toolkits. Adding desktops and laptops to that mix seems obvious.
And it goes the other way. The iPad Pro will probably benefit by gaining support for pointer input.
Same experience for me. The University of Washington headache clinic recommended Vitamin D and Magnesium supplements and it made a marked difference in my mood. Turns out having constant mild headaches is pretty depressing.
http://www.gutenberg.org/ebooks/1342
:)