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…
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…
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?
> Say if I press Cmd+Space on a Mac and type "Facebook" in Spotlight, it immediately begins downloading the native OS X Facebook app That's exactly what Windows 10 does. http://imgur.com/EqvATwL
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.
Because the grip and weight balance will make one-handed reading more comfortable.
Performance should be a pretty big concern for UI frameworks. Would be interesting to see some benchmarks.
https://github.com/ReactWindows/react-native/blob/ReactWindo... Looks like it evaluates the JS and creates XAML elements programmatically using C#.
Yea, looking at this made me realize how uncomfortable my Paperwhite is one-handed. When laying down I usually end up holding it awkwardly with my thumb underneath and my pointer finger straight up the bezel. It's…
Runtime heap usage.
Runtime memory usage and startup perf is better for C++ XAML apps.
Why does this generate C# instead of C++?
And now your messenger app needs a launcher, switcher, notification manager, search, per-app settings pages, etc. And maybe its own process model/scheduler, to prevent rogue apps from slowing down the messenger app. And…
Let me get this straight. - The phone OS has a shell, usually written in native code. - The messenger app runs on top of the shell, usually written on top of some type of VM. - The messenger app contains a web browser…
First browsers became OS's, now you want messenger apps to become OS's? How many layers of cruft do we need?
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…
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…
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?
> Say if I press Cmd+Space on a Mac and type "Facebook" in Spotlight, it immediately begins downloading the native OS X Facebook app That's exactly what Windows 10 does. http://imgur.com/EqvATwL
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.
Because the grip and weight balance will make one-handed reading more comfortable.
Performance should be a pretty big concern for UI frameworks. Would be interesting to see some benchmarks.
https://github.com/ReactWindows/react-native/blob/ReactWindo... Looks like it evaluates the JS and creates XAML elements programmatically using C#.
Yea, looking at this made me realize how uncomfortable my Paperwhite is one-handed. When laying down I usually end up holding it awkwardly with my thumb underneath and my pointer finger straight up the bezel. It's…
Runtime heap usage.
Runtime memory usage and startup perf is better for C++ XAML apps.
Why does this generate C# instead of C++?
And now your messenger app needs a launcher, switcher, notification manager, search, per-app settings pages, etc. And maybe its own process model/scheduler, to prevent rogue apps from slowing down the messenger app. And…
Let me get this straight. - The phone OS has a shell, usually written in native code. - The messenger app runs on top of the shell, usually written on top of some type of VM. - The messenger app contains a web browser…
First browsers became OS's, now you want messenger apps to become OS's? How many layers of cruft do we need?