9 ms·
Microsoft Project Reunion: an evolution of the Windows developer platform
- aspenmayer 6y ago'At Build 2020 [1] today, Microsoft unveiled Project Reunion [2], its latest attempt to unify the Windows developer platform by reducing fragmentation between Win32 APIs and Universal Windows Platform (UWP) APIs. Microsoft also promises Project Reunion can modernize existing apps with the latest functionality, whether they’re built using C++, .NET (including WPF, Windows Forms, and UWP), or React Native. Additionally, it can decouple the APIs from Windows via tools like NuGet, and it brings new WinUI 3 and WebView2 releases.'[3] Possibly related: Windows Package Manager Preview https://devblogs.microsoft.com/commandline/windows-package-manager-preview/ https://devblogs.microsoft.com/commandline/windows-package-m... https://github.com/microsoft/winget-cli https://github.com/microsoft/winget-cli [1] https://mybuild.microsoft.com https://mybuild.microsoft.com [2] https://github.com/microsoft/ProjectReunion https://github.com/microsoft/ProjectReunion [3] https://venturebeat.com/2020/05/19/microsofts-project-reunion-bridges-win32-and-uwp-divide-again/ https://venturebeat.com/2020/05/19/microsofts-project-reunio...
- kroltan 6y agoDon't get me wrong, but are you associated with the project or Microsoft?
- itsspring 6y ago16 points, 16 minutes, and OP posted that 16 minutes ago? Sure seems like a reasonable question to ask, but OP's profile seems to point at a negative answer. That said, a single-sentence copy/paste from the article isn't very substantial
- deleted 6y ago[deleted]
- moron4hire 6y agoWhy would it matter? Can't an MS dev be proud of their work and want to share it, without being accused of being a "shill"?
- kroltan 6y agoWhen I commented, the comment in question had a very generic market-speech, and as a moderator of other internet communities, my "spider-sense tingled" so to speak. As it stands now the comment is much more productive.
- aspenmayer 6y agoIt was a quote that I hadn’t yet cited. I had no intention to be ambiguous so I do apologize for the confusion.
- aspenmayer 6y agoNo, just a long time user. Own no stock, no business interest in MSFT other than supporting users in a professional context.
- kroltan 6y agoFair enough! It's just that your comment before the edit sounded a bit generic. Sorry for the annoyance!
- Phil-bitplex 6y agoI have re-read the readme about 5 times now, and I'm still not really sure what it is. I _think_ its an API wrapper to make functionality available in older versions of windows, is is only in newer versions of windows? Or maybe other platforms that support UWP? It feels like the readme is written in startup-speak, where I was expecting it to be a little more... developer-y?
- ocdtrekkie 6y agoBasically, this is about ensuring all of the different Windows, .NET, etc. APIs that Microsoft announces work and are available on any of the different flavors of Windows app development you can do. The main thing is that a large category of APIs are available to UWP apps (think Windows 8/10 Modern apps) that aren't available to desktop apps, and Microsoft has been trying to close that gap, since developers have basically said no to rebuilding their apps from scratch for Microsoft's newer app platforms. The original goal was to force people to move to UWP, which is mobile friendly, processor architecture independent, etc. But the shift was too hard so nobody did it. If all of the APIs are available everywhere, legacy Win32 apps can continue to evolve, and at the same time, Win32 and UWP apps coming closer together makes an eventual shift over to UWP more practical because it won't require starting from scratch.
- kungato 6y agoI think this is similar to how when they started adding features to angular 1 which resemble concepts from angular 2 so that people could start considering upgrading
- contextfree 6y agoI agree it's confusing. But here's the intention as far as I can tell: UWP was originally "monolithic" and "closed" in several respects: your app had to either adopt all UWP facets (be a "UWP app") or none (be a "Win32 app"), new APIs only shipped with new Windows releases, the implementations were entirely closed source, etc. In the past few years they've started to take pieces of what used to be UWP and pull them out into separate components. Unlike the monolithic UWP platform, these components can be adopted independently by Win32 apps without having to adopt all the other components at once, their runtimes can be distributed with your app outside of Windows and run at least a few versions back, their implementations are partly or wholly open source, they do planning and design reviews in the open on github, etc. So far, the components they've done this with have been * WinUI (a decoupling of the UWP UI framework) * MSIX (a decoupling of the UWP packaging system) * C++/WinRT, C#/WinRT and Rust/WinRT (a decoupling of the UWP object system and language bindings) The "new" Project Reunion is basically an umbrella name for these decoupled UWP components, a declaration of their intent to decouple the rest of UWP in similar fashion, and a new github repository for planning this and designing the future evolution of the Windows developer platform in general. So the repository has issues posted by Microsoft developers about how the UWP app lifecycle and resource formats can be decoupled, for example.
- cs702 6y ago> Project Reunion is our vision for unifying and evolving the Windows developer platform to make it easier to build great apps that work across all the Windows 10 versions and devices* people use.* I'm always a bit skeptical of projects that seek to harmonize or standardize APIs across different kinds of hardware devices, not for the benefit of users, but for the benefit of software developers. The visions behind such projects often seem to produce elegantly designed software platforms, like Windows 10 Mobile[a] and Ubuntu Touch[b], for which there is actually no user demand. Did end-users, i.e., regular people, ask for Project Reunion? -- [a] https://en.wikipedia.org/wiki/Windows_10_Mobile https://en.wikipedia.org/wiki/Windows_10_Mobile [b] https://en.wikipedia.org/wiki/Ubuntu_Touch#Ubuntu_Mobile https://en.wikipedia.org/wiki/Ubuntu_Touch#Ubuntu_Mobile
- tasogare 6y agoThe Windows platform is extremely fragmented since Win10: not only there is different API and execution models (Win32, UPW) but also each new Win10 build brought new API that were not available on previous versions. Even as someone who program mainly in C# (on Mac/Linux) and some knowledge about the UWP disaster^W situation this is a mess cery hard to understand and not appealing to develop for.
- ferzul 6y agowhy is it a problem that they release new api's? they couldn't bring them all out before they're written, so the alternative is to batch them up and release them all at once. but then don't you still have a common install base, because the change will be too much for some users who will hold off, a la windows 7/8. as someone doing a little windows dev on the side, the issue for me has been that i don't know whether uwp or win32 is the better (future proof) choice. i guess when one of the main distinctive features of your os is that it is backwards compatible, it is hard to change. (i noticed BN_UNPUSHED is documented as being included for compatibility with 16-bit versions of Windows before 3.0.)
- Hamcha 6y agoI as a developer asked for it. Always tried to develop UWP but Microsoft has made it the hardest possible to. SDKs for UWPs are many and each of them is someway incompatible with their other revision. There used to be at least 3/4 competing different "versions" of "Universal" windows platform SDKs at the same time, each of them with different features and device support (including the latest which is like Windows 10 but only from certain major updates). Sadly, even this just looks like XKCD #927 all over again. It's honestly so ironic how little universal any of it is, in the end.
- aspenmayer 6y agoIs this Google Wave coming back in the form of Office.com? Open-source! Definitely a different Microsoft than the one I grew up with. Announcement support page https://support.microsoft.com/en-us/office/get-started-with-fluid-framework-preview-d05278db-b82b-4d1f-8523-cf0c9c2fb2df https://support.microsoft.com/en-us/office/get-started-with-... In the news https://www.theverge.com/2020/5/19/21260005/microsoft-office-fluid-web-document-features-build https://www.theverge.com/2020/5/19/21260005/microsoft-office... 'Microsoft is creating a new kind of Office document. Instead of Word, Excel, or PowerPoint, the company has created Lego blocks of Office content that live on the web. The tables, graphs, and lists that you typically find in Office documents are transforming into living, collaborative modules that exist outside of traditional documents. 'Microsoft calls its Lego blocks Fluid components, and they can be edited in real time by anyone in any app. The idea is that you could create things like a table without having to switch to multiple apps to get it done, and the table will persist on the web like a Lego block, free for anyone to use and edit. '“Imagine you could take those Lego pieces and put them in any place you wanted: in emails, in chats, in other apps,” explains Jared Spataro, head of Microsoft 365, in an interview with The Verge. “As people work on them, they will always be updated and contain the latest information.” 'Microsoft’s Fluid Framework sounds a lot like Google Docs, but it’s actually Google Docs on steroids. Microsoft is so confident it has built the future of productivity, it’s now open-sourcing its Fluid Framework so the rest of the world can help shape what it has created. Some Office.com users will even be able to start getting a taste of this Fluid future in the coming months.'
- Ididntdothis 6y agoWrong thread.
- aspenmayer 6y agoI'm the OP. I meant to post this where I did. Edit: you were right I was wrong apologies
- btmiller 6y agoYou mean your other post? https://news.ycombinator.com/item?id=23236287 https://news.ycombinator.com/item?id=23236287
- btmiller 6y agoMicrosoft seems to have tried to unify their developer story in many incarnations now. So my biggest question is, why will this one succeed where others have failed? I see absolutely no evidence to suggest this is better than previous attempts.
- draw_down 6y agoYeah, this really has the flavor of that webcomic about "14 competing standards -> one to unify them all -> 15 competing standards"
- wvenable 6y agoMicrosoft wanted to unify their developer story around UWP (in all it's incarnations) and that never took hold. This is a realization of that and re-focus on bringing all their development frameworks up to modern standards (even Winforms!) Supporting developers were they are is likely to be much more successful than supporting developers were they wanted them to go.
- criddell 6y agoThe consumer Windows ecosystem (excluding games) feels moribund. When is the last time that anybody was excited about some new or improved Windows program? Everything interesting seems to be happening either on mobile or on MacOS. There's still lots going on in the commercial / enterprise space, but that stuff is either old and Win32 or new and in the browser. Who is using UWP?
- pjmlp 6y agoAnyone that wants to access any new Windows API introduced since Vista, where they re-focused on COM to deliver the ideas that failed with .NET on Longhorn. So if you are using pure old style Win32, you will be using a view of the computing world stuck in Windows XP.
- criddell 6y ago> you will be using a view of the computing world stuck in Windows XP That's kind of what I was getting at when I said the Windows ecosystem (excluding games) is moribund.
- sylens 6y agoThis is all about fixing a mistake that never should have been made. They did the UWP split around the time of Windows 8 and since then have tried to prop up the Windows Store with Windows Mobile ports, XBox games, and other ventures. It’s good to see them finally recognize that the Microsoft Store wasn’t going to go anywhere.
- tasogare 6y agoYep, and this fiasco was easy to predict: of course nobody (enterprises and hobbyists) would rewrite decades of legacy code to a platform that 1. wasn’t supported on the most deployed Windows version at the time 2. didn’t provide feature parity with Win32 3. imposed an ugly toolkit not adapted to desktop apps (i.e. 100% of Windows device at the time, and probably still >90% nowadays) and 4. imposed a distribution model with a very significant "store tax".
- wvenable 6y agoThe UWP project was all about Windows Phone -- it was a platform for running more constrained and less battery-heavy applications on a phone while also allowing those apps to run on the desktop. When their phone platform imploded, UWP suddenly didn't have a real market.
- sbarre 6y agoI was hoping this was about a new open-source version of MS Project =(
- mrpippy 6y agoThis seems more like codifying some principles/guidelines between a couple of new APIs (and hopefully everything going forward), rather than anything actually new: * can be used in UWP and Win32 apps (with no package required for Win32) * supported on Windows 10 versions going back several years
- nicoburns 6y agoThe list of supported languages is pretty interesting. Looks like Microsoft is pretty serious about making Rust a first class citizens for it's Windows APIs: > C++, Rust, C#, and JavaScript
- qzw 6y agoWould definitely be nice to see Microsoft put more resources into supporting Rust. Go has Google’s backing and Swift has Apple’s. Would be interesting if Microsoft fully embraces Rust, but hopefully without the “extend and extinguish” part.
- steveklabnik 6y agoThey already do support Rust in a few ways, but I would always welcome even more support for sure :)
- LyalinDotCom 6y agoThe first thing you as a developer can start exploring today that is part of "Project Reunion" is WinUI 3.0 Preview 1: https://blogs.windows.com/windowsdeveloper/2020/05/19/introducing-winui-3-preview-1/ https://blogs.windows.com/windowsdeveloper/2020/05/19/introd...
- tzs 6y ago> Project Reunion is our vision for unifying and evolving the Windows developer platform to make it easier to build great apps that work across all the Windows 10 versions and devices people use. I just want it to be like it was in 1998. Want to learn how to program for Windows 95, 98, or NT back then? Buy Programming Windows 5th edition by Charles Petzold, read it, and you are most of the way there. Add Advanced Windows by Jeffrey Richter if you need more lower level knowledge. If you needed to support Win 3.1, you had Petzold's Programming Windows 3.1 for that. (...and Petzold's Programming the OS/2 Presentation Manager if you wanted to branch out a bit). Just get Petzold to write one of these for Windows 10 and I'll be happy.
- troughway 6y agoHe did, didn't he? Programming Windows 6th edition is Win8+, and I believe in this one (or another one) he delves into additional APIs like DirectWrite and whatnot.
- ripley12 6y agoYep! I've been using the 6th edition recently, it's great for understanding the principles of UWP development. It's still remarkably useful for a book that was published in 2013, but we are probably overdue for a "version 6.5".
- tzs 6y ago> It's still remarkably useful for a book that was published in 2013, but we are probably overdue for a "version 6.5". That reminds me of a site I wish existed. It would mainly just present a table listing tools and technologies in column 1, and a year in column 2. The year is the earliest year that books written for that tool or technology will still be mostly applicable to the current version. For example, suppose you would like a book about Postfix (the SMTP server). There are a few books on it, still available new. Hildebrandt and Koetter's "The Book of Postfix" (2005). Dent's "Postfix The Definitive Guide" (2003). Blum's "Postfix" (2001). Does Postfix change slowly enough that some of those are still worth reading? That's what the site I want would tell you. Of course it would be fine if the site had more detail. It might say things like for technology Foo books after 2016 should be fine, books from 2012 to 2016 should be fine except they will be missing major feature X and Y, books from 2008 to 2012 will be using an older, very different configuration system, and books older than that will be pretty much useless.
- nvr219 6y agoWhy is Microsoft so bad at naming things.
- fred_is_fred 6y agoI assumed this was party planning for the original team who wrote Microsoft Project and clicked just to see if there was a Gantt chart to show who was going to buy beer and the estimated lead time.
- ourmandave 6y agoWhat’s different this time? Microsoft has been on a years-long journey to unify the APIs in Win32 and UWP, adding more common APIs and interoperable code between the two. Still, every time Microsoft tries to improve the situation, developers have to wait for the latest version of Windows. This time, Microsoft is borrowing an idea from the web — polyfill — with the introduction of packages. A polyfill is a piece of code that provides modern functionality on older browsers that do not natively support it. As Microsoft introduces new APIs, developers link against a package, and if you’re on an older version, Microsoft will polyfill the functionality as best it can to use in the new version. The best part is that these packages will work from a Win32 or UWP app. The collection of packages thus becomes a common API service between Win32 and UWP. Best of all, Microsoft can do this across its 1 billion devices, immediately. Microsoft EVP Rajesh Jha explained the result in a briefing ahead of Build 2020. From this article: https://venturebeat.com/2020/05/19/microsofts-project-reunion-bridges-win32-and-uwp-divide-again/ https://venturebeat.com/2020/05/19/microsofts-project-reunio...
- WrtCdEvrydy 6y agoPolyfills are a problem since you have to bundle them even if your version supports the new features... unlike the web where you can use the user's browser info to send them the correct polyfill these new applications will get larger and larger.
- nicoburns 6y agoHmm... it works pretty well for android (Android Support Library). I think it only compiles in the bits you use which helps keep the app size down.
- applecrazy 6y agoI believe that’s the case for modern JS polyfills (if you use a bundler)
- lallysingh 6y agoAnother DLL? Does it matter?
- dmix 6y agoJVM, part 20.
- diimdeep 6y agoMicrosoft - support every API we ever had. Apple - deprecate old and focus attention on new. I beleive in latter. Are you?
- dboreham 6y agoParsed that as "Microsoft Project" Reunion. Like a dinner where the devs and pms from the Project planning application reminisce about old times, before daily standups and stories and sprints and...scrum masters.
- smitty1e 6y agoPrecisely. And then I wondered who hated themselves enough to spend more time with that application than they were paid fat piles of cash to do.
- rokstar 6y agoWinRT?
- legulere 6y agoWebView2 seems like an interesting replacement for electron.
- dstaley 6y agoWebView2 isn't a replacement for Electron; it's a replacement for the Internet Explorer powered WebView component that's been a part of Windows 10 since the beginning. WebView2 doesn't have the same level of platform APIs that Electron provides. While you totally could build a similar app using WebView2 as you could with Electron, you're going to have to build all the non-web bits yourself.
- cl0rkster 6y agosounds like they are serious about making an interoperability layer between older programming constructs so you can run .net core code on older frameworks am i missing something other than the politics? admittedly this is pure speculation (TLDR... i mean... it's a corporate github repo with an unfathomable number of enormous minds contributing to it), but i would think something like .net core 1.1 would be the initial target also... to head of the parenthisized joke above... i was also too lazy to research it more. i told my boss about it, though. he's smart... and in charge of how things like this impact my life