Aleman360

Writing an outline of a book is more analogous.

Not sure if I agree. I find that coming up with good interfaces is often more of a creative challenge than the implementation. API's are worthy of some sort of protection since ease of use is a definite competitive advantage.

Also, you can easily screw your perf with bad interfaces (especially in C++). E.g., not templatizing, requiring extra allocations, type impedance mismatches, vtable bloat, etc. The interface certainly affects how the machine executes your code.

Sounds like Windows 8 where the desktop was an "app" on the Start screen.

They can just change their name.

In a word where most new code is JavaScript, just use auto everywhere. It will be OK.

> If it were only localism, there would be localities that were fantastic at investing in their own infrastructure.

Seattle. Great water, renewable energy, lots of transit investment.

I love it when people use generic names and then add a two word comment describing what it is.

I also love it when people use primitives for time spans along with the units in the name or comment instead of TimeSpan/std::chrono.

You may be paying for it even if not using it, but you have to account for the environmental savings. But people care less about stuff that's harder to measure.

Agreed, they're all same-ish now.

Seems like a leaky abstraction. Did their interfaces have a way to account for differences in latency and failure modes, or was that hidden?

That's more likely explained by the fact that PS4 launched $100 cheaper and is more powerful.

UWP has XAML which is native and declarative. It's what the Windows version of React Native targets.

Silverlight is actually a descendant of WPF.

WPF > Silverlight > UWP

All your skills are transferable.

UWP has the latest version of XAML, implemented natively this time and with a faster rendering backend. WPF lives on in spirit.