Linked by Thom Holwerda on Thu 5th Mar 2009 13:27 UTC
Windows For Windows 7, Microsoft has made some changes to User Account Control to counter the criticism that UAC was too intrusive. It didn't take long before several holes were poked in Windows 7's default UAC settings, and now one is left to wonder: is it wise to sacrifice security for (perceived?) usability? Ars has an editorial that deals with this question.
E-mail Print r 8   · Read More · 93 Comment(s)
Thread beginning with comment 351826
To view parent comment, click here.
To read all comments associated with this story, please click here.
jabbotts
Member since:
2007-09-06

Far as I can see, winNT (distro) already has a graphic interface. Did you mean seporating the graphic and functional layers of most programs?

Back-slash vs forward slash is not a huge issue personally but I can understand how making it a second class citizen on the keyboard causes grief. My own issue is purely habbit, after so many hours at the server prompt, it's not surprising that my first Windows cli command path returns an error due to using the wrong slash key. (I also giggle every time "/h" brings up a list of Unix like command switches; see shutdown /h for example.)

winNT (kernel) if as discussed in the article could be far better implemented by fixing the userland around it.

I make enough noise about specifying distributions rather than "Linux" as a blanket term. I'm equally willing to look at winNT-kernel separate from winNT-distribution.

Now, if Microsoft can fix it's corporate culture and allow the developer tallent they've collected to actually be talented; win8 could be very much worth a look. (I think it may be too late for some of the "design decisions" in win7.)

Reply Parent Score: 1

google_ninja Member since:
2006-02-05

Microsoft is between a rock and a hard place. The rock is that their security systems need to be enforced more then they are, the hard place is the billions of dollars customers have invested in the platform in terms of legacy software that relies on them not being enforced.

As of windows XP, nothing at all should have ever been writing to anyting but HKEY_CURRENT_USER in the registry, and nowhere on the disc except for AppData in the user folder. If it is a corporate app designed for NT, it should never have had any excuse to do that.

Reply Parent Score: 4