Is Microsoft Working Towards NT, Silverlight/.Net Everywhere?

Since the big Windows news last week was the announcement that the next version of Windows will run on ARM, this one kind of slipped in under the radar. It’s a rumour, but confirmed by different people: there will be a new application model in Windows 8, currently named Jupiter, while thee will also be a tile-based interface for tablets. It seems like the pieces of the puzzle are all falling into place: Windows NT everywhere, Silverlight/.Net everywhere.

The tile-based interface would appear to be similar to what’s currently available on Windows Phone 7, but without any details – let alone screenshots – it’s impossible to tell. According to Paul Thurrot, the interface is codenamed Mosh, and will only be available on devices like tablets. In other words, it’s not a replacement, but an alternative.

All this seems to fit with the idea that Microsoft is trying to consolidate all form factors into one – as in, everything will be running Windows NT, no matter the screen size, no matter the architecture. Not only would this be a serious cost-cutting measure, but it would also allow for faster propagation of new lower-level features throughout all the different form-factors currently supported by Windows NT and Windows CE. In other words, it’s the Linux strategy.

The rumours around Jupiter are possibly more interesting. “Windows 8 will also include a new app model codenamed Jupiter that will target a new Windows Marketplace app store,” Thurrot claims, “The app store will provide access to new, Silverlight-based ‘immersive’ applications that are deployed as AppX packages (.appx).”

“The Windows and Office teams are betting very heavily on this new app type, according to my source, and development has already begun using a beta version of Visual Studio 2012,” he adds, “These apps can be written in C#, Visual Basic, and even C++.”

The Jupiter rumours were confirmed by another Microsoft insider, Mary-Jo Foley. After talking to a few of her sources inside the company, she’s gained a pretty decent insight into what Jupiter actually is.

“Jupiter is going to be a new user interface library for Windows, built alongside Windows 8. It will be a thin XAML/UI layer on top of Windows application programming interfaces and frameworks for subsystems like graphics, text and input,” she details, “The idea is Jupiter will bring support for smoother and more fluid animation, rich typography, and new media capabilities to Windows 8 devices.”

As Tess, Kroc, and I already discussed in the podcast, it seems like to me that Microsoft might be using this as a means to coerce developers away from the current development models of Windows. All they need to do is include the Marketplace application store with every copy of Windows 8, and limit the store to Jupiter applications only. Then, detail that for Windows 9, the various application stores – Windows Phone, Xbox, and Windows (and Surface?) – will be unified, and you’ve got a pretty decent audience for developers to target.

Of course, we won’t know anything for sure until Steven Sinofsky allows for the veil to be lifted, but in all honesty, it looks like as if Microsoft’s Windows strategy is finally culminating into something good. This process started with the slow untangling of the Windows codebase somewhere around 2002 and 2003, and it looks like it will culminate into Windows NT everywhere, Silverlight/.Net everywhere, all served by a single, unified application store.

And thus, backwards compatibility would cease to be a major issue.

83 Comments

  1. 2011-01-10 5:22 pm
    • 2011-01-11 11:44 am
  2. 2011-01-10 5:33 pm
    • 2011-01-10 5:35 pm
      • 2011-01-10 5:46 pm
    • 2011-01-10 7:37 pm
      • 2011-01-10 7:49 pm
  3. 2011-01-10 5:42 pm
    • 2011-01-10 5:43 pm
      • 2011-01-10 5:47 pm
    • 2011-01-10 5:56 pm
      • 2011-01-12 10:41 am
  4. 2011-01-10 5:50 pm
    • 2011-01-10 5:52 pm
      • 2011-01-10 5:55 pm
        • 2011-01-10 9:15 pm
          • 2011-01-10 9:25 pm
          • 2011-01-10 9:44 pm
          • 2011-01-10 9:31 pm
          • 2011-01-10 9:44 pm
          • 2011-01-10 10:03 pm
          • 2011-01-11 12:23 pm
          • 2011-01-11 8:18 pm
          • 2011-01-12 10:34 am
          • 2011-01-12 9:09 pm
          • 2011-01-12 10:42 am
          • 2011-01-12 9:11 pm
        • 2011-01-11 12:26 pm
  5. 2011-01-10 6:03 pm
    • 2011-01-10 6:15 pm
  6. 2011-01-10 6:31 pm
    • 2011-01-11 12:11 am
      • 2011-01-11 12:14 am
        • 2011-01-11 12:20 am
          • 2011-01-11 12:29 am
          • 2011-01-11 12:58 am
          • 2011-01-11 1:03 am
          • 2011-01-11 12:33 pm
  7. 2011-01-10 6:34 pm
  8. 2011-01-10 6:55 pm
  9. 2011-01-10 7:26 pm
  10. 2011-01-10 10:11 pm
  11. 2011-01-10 10:15 pm
  12. 2011-01-10 10:41 pm
    • 2011-01-10 10:50 pm
      • 2011-01-11 12:15 am
        • 2011-01-11 12:16 am
          • 2011-01-11 12:29 am
          • 2011-01-11 5:42 am
          • 2011-01-11 12:27 pm
          • 2011-01-12 3:32 am
          • 2011-01-12 10:18 am
        • 2011-01-11 1:35 am
          • 2011-01-11 6:20 pm
          • 2011-01-12 5:45 pm
          • 2011-01-13 12:42 am
      • 2011-01-11 6:11 pm
      • 2011-01-12 2:27 pm
  13. 2011-01-11 3:21 am
  14. 2011-01-11 8:51 am
  15. 2011-01-11 11:50 am
    • 2011-01-11 12:41 pm
      • 2011-01-11 2:22 pm
        • 2011-01-12 2:36 am
          • 2011-01-12 9:48 am
          • 2011-01-12 10:05 am
          • 2011-01-12 2:16 pm
          • 2011-01-12 10:21 pm
    • 2011-01-12 5:47 pm
      • 2011-01-12 8:33 pm
  16. 2011-01-11 1:53 pm
    • 2011-01-11 3:06 pm
      • 2011-01-11 7:16 pm
        • 2011-01-11 7:42 pm
    • 2011-01-12 10:27 pm
  17. 2011-01-11 2:38 pm
  18. 2011-01-11 9:56 pm
    • 2011-01-12 5:54 pm
      • 2011-01-12 7:17 pm
    • 2011-01-12 10:31 pm
      • 2011-01-12 10:51 pm
        • 2011-01-13 1:02 am
          • 2011-01-13 2:24 pm