14 votes2 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
The important aspect of native apps for me is efficient compilation to native code. Bytecode is OK, AOT even better. Of course what matters is the end result: memory usage and performance.
From my business's point of view, once we have covered all the platforms, we would not release a webapp because anyone can get a native app, which is better (performance, memory, reliability).
If we didn't have coverage, then yes a webapp would be worthwhile. Webapps are a cross-platform technology, that make it easy to reach many platforms, albeit with a low-quality solution. But if we can reach those platforms natively, why would we want a webapp?
This project is mostly done. Xamarin.Forms already has most of these items, with only 2. Legacy Windows to come (and 3. and 6. in preview). 7. is not on the roadmap but once you have all the platforms covered with native solutions, you do not need a web solution. https://github.com/xamarin/Xamarin.Forms/wiki/Feature-Roadmap
We’re making real progress against this area – slowly but surely. If you haven’t seen Visual Studio 2017 RC (or later) yet, check it out at http://visualstudio.com. We are eradicating many of the separate items that come from Microsoft, although we will continue to list third-party dependencies individually (for example, if I used the Visual Studio installer to get the Android SDK, we presume you might want to be able to uninstall that without relying on Visual Studio).
Let us know what you think… Thanks for the feedback, Tim Sneath | Visual Studio Team
There is far too much old and obsolete junk installed with the Visual Studio installer, even with VS2017. Visual C++ redistributables going all the way back from 2017 to 2005! The same goes for SQL server. And for the .Net Core SDK. And for the .NET Framework SDK and Multi-Targeting pack. So many old versions are installed. And x86 support is not needed in a default installation either.
Suggestion for a general policy: If possible, only include the latest version of an SDK. If VS components don't work with the latest versions, then try to update them. If that's not possible, release the previous version. Never put anything before the previous version in a default installation. Anything else can be selected as an option or downloaded on demand.