News for hackers. Stuff that matters.
Re:What happens when you launch Google Chrome for the first ... by pjmlp on Tuesday August 27, 2019 @03:09AM (#20806977)
Windows has been on the sandbox path since Windows 8.

Every release gets a bit more of that, regardless how many feel about the store or UWP API in general.

Re:What happens when you launch Google Chrome for the first ... by raxxorrax on Tuesday August 27, 2019 @03:45AM (#20807158)
I don't want to only use trusted sources from any software store. If UWP had provided sensible deployment options, it wouldn't be as dead as it is.

Hell, personal firewalls provide a better sandbox solution, at least for network access, even if that is not really their intended function.

Be that as it may, I think good privacy laws and holding software manufacturers accountable is part of a solution. That software more and more behaves like worms regarding to user data is a more recent development.

Re:What happens when you launch Google Chrome for the first ... by pjmlp on Tuesday August 27, 2019 @04:27AM (#20807376)
UWP is not dead, every Windows release adds more API space, React Native for Windows uses UWP, Windows 10 drivers now use UWP APIs as well (Universal drivers), WinUI uses UWP, XAML Islands use UWP, ...

WinUI is also the official replacement for MFC, which triggered the rewritte of some UWP components into C++/WinRT from .NET Native.

Windows store supports side loading since Windows 8.1, and MSIX packages have replaced APPX and MSI as the future of Windows package formats.

Win32 APIs are frozen in amber since Windows 7.

Re:What happens when you launch Google Chrome for the first ... by raxxorrax on Tuesday August 27, 2019 @07:34AM (#20808450)
Maybe. I am not really happy with it to be honest. Win32 is old and I thought WPF would be a real alternative. It did many things better than classical APIs, but I was never really into XAML and it was dropped just after a few years. I took a quick look at UWP which uses XAML in a different way, but I wasn't really convinced by it.

I am not interested in side loading anything. I have just no interest to use an API that is abused to promote a proprietary store and an OS because I only see disadvantages in that. UWP may have changed by now, but for me it is too late. I have switched to other technologies and are pretty happy with them. If windows continues to be SaaS, I will not develop for it. Even if its legacy might continue for a few decades.

If the primary form of deployment is a store, I could as well use Apple. Although their store isn't really shining on Mac OS as well. I believe there are good reasons for that.

Windows as a platform had many advantages, but it seems to me that MS threw that away to emulate others. A futile strategy in my opinion.

Re:What happens when you launch Google Chrome for the first ... by pjmlp on Tuesday August 27, 2019 @08:55AM (#20809020)
Have you been paying attention regarding Apple platforms?

> Beginning in macOS 10.15, notarization is required by default for all software.

Taken from https://developer.apple.com/documentation/security/notarizin...

Web, iOS, watchOS, iPadOS, Android, ChromeOS all use some form of sandboxing.

So unless your alternatives are the 1% GNU/Linux desktop market, sandboxes are here to stay.

Re:What happens when you launch Google Chrome for the first ... by raxxorrax on Tuesday August 27, 2019 @09:15AM (#20809200)
That will result in a lot less software for mac OS. Since there are many applications that certainly will not spend anything on developer ids, e.g. most open source software there will simply be less builds for the platform.

ChromeOS supports android apps, but yes, I would state that iOS, chromeOS and android are really bad operating systems.

Re:What happens when you launch Google Chrome for the first ... by pjmlp on Tuesday August 27, 2019 @09:37AM (#20809428)
Regarding ChromeOS:

"Linux for Chromebooks: Secure Development"

> Learn how Linux for Chromebooks (Crostini) gives you a secure sandbox for development. Through a variety of demos, this talk will explain the architecture underlying Linux for Chromebooks and the design decisions that keep it easy to use.

https://www.youtube.com/watch?v=pRlh8LX4kQI

And Android:

"Adopting the Arm Memory Tagging Extension in Android"

https://security.googleblog.com/2019/08/adopting-arm-memory-...

"https://developer.android.com/distribute/best-practices/deve...

https://developer.android.com/distribute/best-practices/deve...

"Improving Stability with Private C/C++ Symbol Restrictions in Android N"

https://android-developers.googleblog.com/2016/06/improving-...

"Android NDK Native APIs"

https://developer.android.com/ndk/guides/stable_apis

Re:What happens when you launch Google Chrome for the first ... by AnIdiotOnTheNet on Tuesday August 27, 2019 @08:23AM (#20808789)
Great. Let me know when that fancy sandboxing tech works for applications I actually use though. Or when UWP catches up with the 1990s and supports portable applications.
Re:What happens when you launch Google Chrome for the first ... by pjmlp on Tuesday August 27, 2019 @08:55AM (#20809028)
Since the introduction of MSIX package format and infrastructure, sandboxing can also be applied to Win32 applications.
Re:What happens when you launch Google Chrome for the first ... by samirm on Tuesday August 27, 2019 @11:41AM (#20810813)
Didn't MSFT just announce they're moving away from UWP in favour of Win32?
Re:What happens when you launch Google Chrome for the first ... by pjmlp on Tuesday August 27, 2019 @11:53AM (#20810984)
Not at all.

That was press articles done by journalists without any clue what UWP is all about, and equate UWP with Windows Phone.

The BUILD 2019 sessions are freely available to anyone that cares to actually learn what the current state of Windows development actually looks like.