In fact, they don't really deprecate things. They may stop pushing something as the new hotness...but VB6 apps still run on windows. Those data access technologies that no one uses anymore...those still work on windows. If you are worried about your investment in time not being the new hotness, well that's one thing. If you are worried about your investment in effort being abandoned...they have done more to support backwards compatibility that I think is even reasonable.
I wonder how Adobe has "kept talent" without rebuilding photoshop?
If you are worried about keeping your personal skills up to date and focused on an area that will earn you personally a living then you should know that some of the most highly paid people I've met in technology code for some of the most niche platforms. I mean serious f*ck off money. Say it with me...AS400. (Or ISeries or whatever the hell it's called now.)
By grabbing their users by the sack and demanding cash they don't deserve under threat of denying access to ones entire body of work.
I had an ex-girlfriend whose employer made a big bet on Silverlight for their web app platform... in 2012. Having to rewrite it all in HTML5 and JS a year later almost put them under.
I dig what you are saying though. They had some very confused messaging about the web as a platform for a long time. They finally stopped the BS, though, and have gone whole hog on the web.
The limitations will show, as more and more usecases will be attempted, and surely many will be addressed.
Personally I hope once the global filesystem concept will be gone, and apps will use isolated or shared storages where shared storage will get explicit access rights for each app/user it is shared with.
The old system had defaults originating from the single user non-multimedia usecases left over as a legacy, but currently we have so many things going on our computers, that privacy/security needs a rethinking of old concepts to cope with new challenges.
I very much hope not, since default and easy global sharing is what makes desktop OSs so very useful, and a lot of this sharing is spontaneous, creative, and ad-hoc. Besides, we already have things like filesystem permissions. By all means have a sandbox for "the untrusteds", but I don't want the equivalent of being forced into the "everything which is not explicitly allowed is forbidden" bureaucracy.
I see your point, that the current solution offers a simple (and vulnurable solution). This is why I have said that these challenges need to be addressed. The current solutions may not be the best, but for an evolution to start we need to make changes, and try different approaches.
I thought that's how Android's filesystem permission works? Each app runs as its own "user", and the FS permission bits restrict what it can access. This is a common solution in the Unix world. The problem on Android is that the filesystem is relatively hidden, and there's no easy way to change those permissions to allow more or less access.
Perhaps having the user as "root", along with all the actually-trusted apps (including those from the OS), and everything else setuid to their own per-app users, would be a useful configuration. Everything that's fully trusted is free to interact, while isolating those which aren't.
I do not like the fact, that an installation of for example a game needs admin rights, and has every chance to access data it should not be able to do.
That's possibly because of a need to install kernel-mode components (might be DRM related). If you're truly paranoid, VMs would be a better choice for isolation. But fundamentally, I don't believe in installing/using/changing apps that I don't completely trust, so perhaps this is a less of a problem for me and I'd rather have everything be "open".
They can if you adopt a user per app model. I thought this is what android/UWP did under the hood.
> I do not like the fact, that an installation of for example a game needs admin rights, and has every chance to access data it should not be able to do.
I doesn't. The biggest cause of this is the default of requiring admin to access program files, even if it's only touching it's own new folder.
Installing off steam happens without admin rights, apart from the VC++ redistributable (why is that a thing?).
It comes with some great benefits though, like easy modding. Imagine if my text editor couldn't access my games folder?
Not that I want to give malware devs any ideas, but I would be surprised if the above never crosses their minds. I suspect the main reason that it hasn't happened to date is that most malware devs are likely gamers and don't want to defecate where they eat.
As for the "great benefits", as much as I like modding, I like my system security a little bit better. There are definitely ways to do modding both securely and easily (and reproducibly) using things kind of like Docker containers and patch overlays, and I'd love it if, say, Valve invested some time into that as a secure platform service. For some of the games it supports Steam Workshop gets sort of, partly there, some of the time...
(But ultimately, I think game developers mostly don't care about security and Steam especially isn't very well incentivized to move out of the dark ages anytime soon. Bringing things back around, I'm hopeful that with the UWP platform exploring things like modding as a service we'll at least see that sort of innovation from Microsoft and the UWP converge towards the best of all worlds, eventually, hopefully...)
[1] Steam has a baroque assortment of DRM and anti-cheat mechanisms, obviously, but only while it is running and even then most of them are passive when a game isn't running. Steam absolutely has no idea what would be legitimate modding to game EXEs (as many mods do that) and what would be trojan-ing. Most people leave Steam running just about all the time, which locks down some of Steam itself, but not everyone does and all it takes is finding one good crash vector for Steam...
[2] Steam also seems to be several anti-practices here because as far as I can tell Steam doesn't ever bother to check if VC Redistributables or DirectX are already up to date on the system, it just spams the installers regardless...
* No app closure callbacks. You don't know if it's suspending or exiting.
* No "are you sure you want to exit? Save/Don't save" dialogs. If you close or crash pray your data was saved, and if it takes a long time to flush to disk...really pray.
* No minimizing/backgrounding to tray icons allowed.
* IMHO save/don't save dialogs are an usability antipattern.
* Tray icons are also something of a remedy of the past. They are now replaced by background operations and live tiles. I can see why those can be problems, I can imagine the usecases you would solve using those tools, but the new app model is build around a slightly different workflow.
But if you do not like the way to solve it as it is intended in the new app model, the solution is: report it/upvote it. If you tell your problems here, then some members of HN community will know it and understand it, but it is unlikely that it will be acted upon by Microsoft. For that you need to have your voice heard on their forums. (eg. feedback app, uservoice...)
Sounds like you have some misconceptions about the UWP/WinRT application lifecycle:
https://msdn.microsoft.com/en-us/windows/uwp/launch-resume/a...
Of course not, because it's supposed to also work on mobile. Does your iPad let applications prevent you from going back to the home screen?
You don't see the problem here? Why do I want the restrictions of mobile phones limiting my desktop applications?
Bashing UWP for advocating a different app model, and different UI design principles is like still using bash in 2016 because you are accustomed to ash from the 70s, and GUIs cannot go to start of line with Ctrl-A, thus saying they are inferior. Change has its positive sides and drawbacks, but in both cases it is mostly for the better.
That's why there is such thing as system settings.
And yes, most desktop users are conscious when they work with files. Windows by default suggests "My Documents" folder as a target destination which is a pretty sane safe choice for all traits of average Joes.
Though you can't submit to store with request for that permission: https://msdn.microsoft.com/windows/uwp/packaging/app-capabil...
Every time I visit family I get to sort out the files scattered around the hard disk.
Funilly enough, in her 70's now she's taught herself to use a computer and can manage documents in the file system.
OpenSSL has had 22 vulnerabilities in 2016 so far [1]
Linux has has 336 vulnerabilities in 2016 so far [2]
[1] https://web.nvd.nist.gov/view/vuln/statistics-results?adv_se...
[2] https://web.nvd.nist.gov/view/vuln/statistics-results?adv_se...
Personally I'd suggest that the trade off is whether the risks of global filesystems are worth it in productivity benefits.
For standard users (non IT-professionals) I think they are not and for IT professionals, in most cases, I think they are.
> The old system had defaults originating from the single user non-multimedia usecases left over as a legacy, but currently we have so many things going on our computers, that privacy/security needs a rethinking of old concepts to cope with new challenges.
I android has proven anything it's that sandboxed applications don't solve this problem.
This to me isn't a great trade off as it relies on the user invoking the process understanding the security risks they're taking, which is a tricky one.
Sure you can do more with sudo, but unless it's the default, most people won't
You're more likely to think twice when you open your flashlight app and it asks "Do you want to allow [Flashlight App] to read all your contacts?"
People starting in a green field will build a web or a mobile app if at all possible. The cases where it isn't are basically games and what used to be called "workstation" apps: big chunky tools like SolidWorks.
Even Adobe have retreated to the cloud, although the tools still run locally.
If it had worked it would have been a smart move, but it was wildly over-optimistic.