News for hackers. Stuff that matters.
Re:Android Killed Windows Phone, Not Apple by kitsunesoba on Sunday July 23, 2017 @11:30PM (#14835698)
I've had interest in writing native Windows (desktop) apps in the recent past, but the confusing messaging/lack of commitment to any particular direction was a real turnoff. On Apple platforms, the only real choice you make is between Swift and Objective-C because either way you'll be using Cocoa. Microsoft would do well to bring that sense of clarity to their dev scene.
Re:Android Killed Windows Phone, Not Apple by flukus on Monday July 24, 2017 @12:45AM (#14835944)
The other problem is that after they finally showed a direction (xaml/UWP) no backwards compatibility was offered, you had to choose between the now deprecated libraries and have an app that worked on windows 7+, or you could choose the new ones and have it only work on windows 10.

Had UWP run on windows 7 we might have seen some more take-up.

Re:Android Killed Windows Phone, Not Apple by WorldMaker on Monday July 24, 2017 @12:15PM (#14839716)
XAML/WPF is close enough to XAML/UWP that you could keep a codebase for both relatively clean and easy to support. (As someone that had to do a bunch of work to maintain a codebase with both XAML/WPF and XAML/Silverlight front-ends, I have very little sympathy to give to anyone that thinks otherwise.)

These days it's getting even easier with Xamarin adding support for WPF, but even without that sort of hand-holding there have always been options.

XAML/WPF is much better than "no backwards compatibility" if you needed to support a UWP-first application on Windows 7. Certainly there were more issues moving the other direction, but particularly/mostly if you had skipped architecting for Silverlight as an intermediate step.

Re:Android Killed Windows Phone, Not Apple by pjmlp on Monday July 24, 2017 @04:49AM (#14836837)
UWP cannot run on Windows 7 because it requires a container model, which I doubt they could just patch on Windows 7.
Re:Android Killed Windows Phone, Not Apple by icebraining on Monday July 24, 2017 @08:24AM (#14837824)
They probably couldn't just port the patches, but there's no reason why they couldn't write a runtime environment on W7, even if it didn't provide the same security guarantees.
Re:Android Killed Windows Phone, Not Apple by tzs on Monday July 24, 2017 @12:23PM (#14839792)
> I've had interest in writing native Windows (desktop) apps in the recent past, but the confusing messaging/lack of commitment to any particular direction was a real turnoff.

Seconded. The previous times I wanted/needed to do Windows development, the first step was ridiculously simple:

  BUY book
  FROM bookstore
  WHERE author = 'Charles Petzold'
  AND title CONTAINS 'Programming Windows'
  ORDER BY publication_date DESC
  LIMIT 1
Heck, that even worked when I briefly thought I'd need to do some OS/2 programming. Just change 'Programming Windows' to 'OS/2 Presentation Manager'.

Nowadays, that gives "Programming Windows Sixth Edition", from 2013, which "focuses exclusively on writing Windows Store applications", for Windows 8, almost always in XAML and C#. He says that "Plenty of other books already exist for writing Win32 desktop applications, including the 5th edition of Programming Windows. I’ll occasionally make reference to Win32 API and desktop applications, but this book is really all about writing new Windows 8 applications".

If I use this book, will it work for Windows 10 also? Are these applications only distributable via the Windows Store or can I host them for download from anywhere? If I want to distribute an application through the Windows Store does it have to be this type, or can I also distribute Win32 desktop applications via the store?

I have one specific application I miss from my old 3rd generation iPad that I have not found a good equivalent for on my Surface Pro 4, and so would like to write it myself, but I have not found a clear explanation of just what my options are, so have not started.