Developing for Windows

12

Now that Microsoft has infuriated and alienated developers by killing UWP, where will new Windows app development come from? What’s the “story” from Microsoft on developing for Windows after this? Is there one? Does anyone even care anymore?

Comments (12)

12 responses to “Developing for Windows”

  1. rob_segal

    There was very little Widows app development before UWP and there will be very little Windows app development after UWP.

  2. hrlngrv

    Considerable cross-OS development. And MSFT itself and Adobe ain't exactly ceasing application software sales.

    The question you have to answer is does UWP give PC users that PC users want?

  3. karlinhigh

    For me, the story would be finding a development environment that is cross-platform and not controlled by an organization that can pull the plug on it. Something looking like Qt or Flutter, maybe.

    • lvthunder

      In reply to karlinhigh:

      Isn't Flutter owned by Google. They could pull the plug at any time. The plug can be pulled on just about everything. You have to pick an environment you like that will produce a product the most number of people will buy.

      • christian.hvid

        In reply to lvthunder:

        Flutter, like almost everything in the developer space these days, is open source. This makes it darn near impossible to pull the plug. Google can pull their own developers from the project, but as long as there's sufficient interest in Flutter, others will step in to fill the void. At worst, the project may become stagnant if developers lose interest. But open source projects are by definition and design very difficult to kill completely.

  4. wright_is

    Most Windows development was Win32 and/or Jave, not many people moved to UWP and it never took off. I'm guessing it will remain in Win32 and Java land for the forseeable future.

    Our ERP supplier has just moved from COBOL to Java, for example.