Print 134 comment(s) - last by kayronjm.. on Apr 17 at 5:26 PM

The truth comes out about User Account Control

Microsoft's Windows Vista operating system has been lambasted ever since it was launched for consumers in January 2007. Diehard Windows users balked at the steep system requirements, sometimes sluggish performance, inadequate driver support, and varying products SKUs at multiple price points.

One feature that has caused quite a bit of controversy with consumers has been the User Account Control (UAC) that is included in Windows Vista. UAC prompts nag users for simple operations such as going to device manager, emptying the recycle bin, or installing/uninstalling an application.

David Cross, a product manager responsible for designing UAC, gave the real reason for UAC at the RSA 2008 conference in San Francisco yesterday. "The reason we put UAC into the platform was to annoy users. I'm serious," remarked Cross.

Cross added that Microsoft's unorthodox method to stop users from wreaking havoc with their systems and to stop software makers from making applications that delved too far into the Windows subsystem was a necessary move.

"We needed to change the ecosystem, and we needed a heavy hammer to do it," Cross added. Cross went on to say that although UAC may be seen as an annoyance to some, but its lasting implications are far more beneficial to Vista users. "Most users, on a daily basis, actually have zero UAC prompts."

Many would say that many users have zero UAC prompts on a daily basis because they have already disabled UAC -- not so says Microsoft. According to Cross, 88% of Vista users have UAC enabled and 66% of Windows sessions do not encounter UAC prompts.

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

RE: Sluggish Performance
By PAPutzback on 4/11/2008 11:59:02 AM , Rating: 2
I think you are comparing different types of coders. I imagine on a new release there is quite a bit of code that wasn't optimized in order to get the product out the door with the plan for the service packs to supply the optimizations.

And a lot of the programmers who do it for a living like myself have so many pending requests you have to spit out code so fast to keep up or find a different living.

A lot of the time your managers might not have coded a day in their life so they have no clue what goes into program. I have had reports take longer to program to get what the user is expecting than a large SSIS package.

And then you have MS spitting out a new platform every six months implemented only half way. They gave us VS 2008 and it doesn't work with reporting services so now you have to maintain two VS installs or run a VMC.

RE: Sluggish Performance
By Locutus465 on 4/11/2008 1:53:22 PM , Rating: 2
Hows the stability of 2008? I've been hesitent to even consider giving it a try considering how flaky 2005 is. VS.Net was my all time fav environment in the 2002/2003 days, starting with 2005 I'd have to say it still integrates all the tools better than anything else I've used, but daaaaaaaaaamn does it sacrafice reliability.

RE: Sluggish Performance
By darkpaw on 4/11/2008 2:50:54 PM , Rating: 2
I've been using 2008 since a bit before launch. I'm really not all that happy with the stability at all. It loves to lock up, especially when using one of the new features split screen code/web view.

If you haven't migrated your code and don't plan on using LINQ, I'd probably stay with 2005. LINQ looks really interesting, but I haven't actually gotten a chance to use it in any work yet.

RE: Sluggish Performance
By jvillaro on 4/11/2008 3:56:03 PM , Rating: 2
Actually I've had a really good experience with it. I've been using it for a while now and even though I'm currently using it on a 1.4 ghz celeron with 768mb of ram the only problem I've had is the expected slowness of this configuration. Specialy because right now I'm working with WPF.

LINQ is not the only reason to change, if you intend to use WCF, WPF and/or WF it's a necesity.

You will have to be carefull when migrating projects with web services or WCF services created on VS2005 so back up just in case and if posible start out with both installed just in case.

RE: Sluggish Performance
By darkpaw on 4/11/2008 4:02:22 PM , Rating: 2
Just out of curiosity (and completely off topic), do you do primary or forms development?

I do ASP.Net work for one project I'm on and I've run into the locks quite a bit when switching from source / view /split on both my primary dev systems. I'm running fairly high end systems (Q6600 desktop and T9300 laptop, both 4gb) and have the issue with both. It does get really annoying after a while.

RE: Sluggish Performance
By jvillaro on 4/11/2008 4:35:49 PM , Rating: 2
Well that could be the difference in our experiences with VS2008. I primary do win forms, wpf forms, services and such. I haven't done anything ASP.NET on VS2008, a partner of mine is starting something and doing some tests but hasn't commented anything. Maybe if we start a full proyect with ASP.NET we could get the problems your talking about.
In WPF the split views are heavy, but again I think it's the machine.
It's not perfect I must admit, but it has worked for me. I remember the same partner say a couple of times VS2008 has locked up on him (although not while using ASP) but VS2005 has done it too so I can't say it's better or worse.

PD: I'm using Windows XP right now if it helps to know. Next week I'll upgrade to a T5550 laptop with 4gb and Vista (all will be running in 64bit) so maybe I'll have an update about all this

RE: Sluggish Performance
By Locutus465 on 4/11/2008 4:28:16 PM , Rating: 2
Hmm, well my company primarly develops a web app (and a few supporting windows apps). So I guess we'll have to be careful with this... Primarly I would like to see us switch to .Net 3.0 so we can take advantage of some OOXML tools in the new framework, but we're doing a huge UI overhaul so it's not the time to be changing out frame works. We'll see what happens, right now the big '05 annoyance is the compiler just getting hung up mid compile, still haven't figured out what's up but it feels like a race condition of some sort.

"Paying an extra $500 for a computer in this environment -- same piece of hardware -- paying $500 more to get a logo on it? I think that's a more challenging proposition for the average person than it used to be." -- Steve Ballmer

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki