> Windows 10 S, announced last week, allows users to install only apps that are distributed through the Windows Store.
What if I want to compile and run my own executables? How does this restriction work?
What if I want to compile and run my own executables? How does this restriction work?
Perhaps if you install a Visual Studio app from the Windows Store and use that to generate an executable, it will somehow sign the executable?
Meta: At what point does the post rate limit get lifted? If I post a couple of comments while browsing the articles and then attempt to reply to a comment with a question, I have already somehow hit the rate limit and I am blocked from posting for a few hours. It seems like there should be an exception for replying to a question on my own comment.
The technologies to look into are APPX, app container, and the Centennial Bridge. Basically, any application can be included in the store. They are using application virtualization from a prior product called APP-V to protect the system from applications tampering with important pieces. It's long over due. It also provides a unified way to update applications through the store.
The store is how they distribute the Ubuntu userland that they ship with WSL...it's very capable.
Up until now they only let people publish a very narrow selection of applications to the store. That strategy failed and now they are going to start pushing Win32 developers to take advantage of the new servicing and packaging system.
It really is very good. I really, really, hope that this doesn't get shot down by herp-a-derp style Microsoft hate.
Also, this doesn't mean that if your friends are using Windows 10 home or pro that they won't be able to install Appx packages. They can. Seriously, it's just a zip file with a manifest. On home/pro and up, users can install Appx packages by double clicking them.
Only Windows 10 S has the restriction that all software installs have to use the store. The thing to watch will be the way that Windows 10 S actually maintains performance and security in ways that the other versions of Win10 can't. As long as users can install services or device drivers as part of an install it's always going to have the same problems.
For something to change it actually has to change. We all know that Windows installers do dumb sh1t. Appx packages run with the same performance and have the same power as normal win32 apps. The only thing they can't do is modify the system in dangerous ways.
Also, there is an Appx for Servers that is being used for Nano server. It does allow service installation and more serious modification of the system...because it has to. It's still a great packaging technology even if you don't use the store or other elements of their plan.
If people would like to access apps from other stores and services, they can switch to Windows 10 Pro at any time.They will be able to code in Visual Basic for Applications. Why teach ancient languages for 70s mainframes in universities? Universities should prepare people for modern offices. Even MIT dropped Lisp long time ago. Why teach multiplication of columns of numbers when you can teach automated Mail Merge in MS Word? Why solve problems from chess when you can make Colourful Agendas with modern charts?
How is this "big issue" almost never brought up in the context of Chromebooks eating up the Education market?
(And of course there are tons of universities where this is not an issue, or students buy a chrome book as a secondary device, or ...)
Then you pay money to upgrade to the real Windows 10.