• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

Windows 7

Direct2D doesn't have a GUI toolkit. You could, I suppose, make a separate render target for each of your windows (ie buttons in my example) but it would be far from ideal and take the complexity of Windows GUI programming to a whole new level.

I don't know why you wouldn't just use GDI and GDI+, then. They are both emulated in software, however on the hardware that is running Vista and Win 7, the performance is no different than XP. Not sure why WPF being managed would be a hinderance to commercial software. Expression Blend 2 is written in WPF and .net, Visual Studio 2010 will be mostly WPF.

PhreePhly
 
I don't know why you wouldn't just use GDI and GDI+, then. They are both emulated in software, however on the hardware that is running Vista and Win 7, the performance is no different than XP.
Haven't you been paying attention? I couldn't use GDI, because it just doesn't support it. GDI+, sure, to a certain extent, but it's **** slow. GDI+ isn't an option when you're using GDI indirectly, like with GUI programming. All the GUI controls in Windows use GDI exclusively. Not much fun if you, say, are trying to draw them on top of glass (because GDI doesn't do alpha, black becomes transparent). Microsoft itself gets around this by using lots of internal custom controls in Windows. In fact, they even have a whole internal GUI toolkit (DirectUI).

My real point though, was that it's all terribly outdated, overcomplicated, and lacking in features. Windows is an extremely difficult platform to develop for, for no good reason (other than legacy). This needs to change. The large number of buggy Windows programs isn't just the developers' fault, it's also Microsoft's.

Also, GDI has hardware acceleration for certain things in 7, XP, and earlier. Vista is a different matter and is actually as much as a hundred times slower in some cases compared with XP, so saying that the performance is no different than XP is not true.

Not sure why WPF being managed would be a hinderance to commercial software.
We've been through this before. Managed code is much slower than native, and uses a lot more resources. It also requires an (or multiple.. ie 3.5 and 4) additional download/redist that is extremely large. WPF itself also has its problems, particularily text rendering. And finally, most of the code out there is unmanaged C or C++, with the odd assembly here and there. You can't expect companies to throw this out.
 
We've been through this before. Managed code is much slower than native, and uses a lot more resources. It also requires an (or multiple.. ie 3.5 and 4) additional download/redist that is extremely large. WPF itself also has its problems, particularily text rendering. And finally, most of the code out there is unmanaged C or C++, with the odd assembly here and there. You can't expect companies to throw this out.

And yet you'd be surprised how many seem to do just that. (note to people running budgets for their business: often times, the cheap alternatives are cheap for a reason)
 
...GDI stuff.

Yea, I guess. I've seen too much software lately which alpha-blending and transparencies, etc. in the UI that is plenty fast. Not sure how those programmers are doing it, but it looks good.


We've been through this before. Managed code is much slower than native, and uses a lot more resources. It also requires an (or multiple.. ie 3.5 and 4) additional download/redist that is extremely large. WPF itself also has its problems, particularily text rendering. And finally, most of the code out there is unmanaged C or C++, with the odd assembly here and there. You can't expect companies to throw this out.

Again, Expressions 2.0 is written entirely in WPF. It is plenty fast. The redistr for the managed code is included with the Vista and Win 7 installs. There may be required updates here and there, but no different than mosta software as is.

I agree with the comment about not expecting companies to throw out old code, but at the same time, you're arguing that MS needs to update theirs. They are and the commercial houses are sticking to the past. Fine, MS still supports the "old and fragile" GDI, so if you want to continue using your old code, stop complaining. If you want to enter the 21st century, start updating your codebase. You being the figurative commercial development houses, not you specifically;)

PhreePhly
 
Well it shuts down properly now the camera is unplugged so it looks like that might have been it.
 
Again, Expressions 2.0 is written entirely in WPF. It is plenty fast.
Compared to what?

And how do you feel about WPF's text rendering that doesn't do pixel snapping and has delayed smoothing, a combination that leads to blurry and laggy text that makes some users physically sick. Yay for progress?

The redistr for the managed code is included with the Vista and Win 7 installs. There may be required updates here and there, but no different than mosta software as is.
Vista includes 3.0, 7 includes 3.5, next year 4.0 will be out. 3.5 is a 200MB redist, 4 will be more.

I agree with the comment about not expecting companies to throw out old code, but at the same time, you're arguing that MS needs to update theirs. They are and the commercial houses are sticking to the past.
Microsoft makes operating systems -- environments for other software to run in. They can push the industry forward, or hold the whole industry back.
 
Compared to what?[/QOUTE]

Compared to Photoshop CS3. On my Core2 2.0 gHz 2 GB laptop, no noticable difference in speed doing somewhat comparable work. The GUI response was no different between either package.

And how do you feel about WPF's text rendering that doesn't do pixel snapping and has delayed smoothing, a combination that leads to blurry and laggy text that makes some users physically sick. Yay for progress?

I haven't noticed the blurry text. I spent hour after hour in Expression and never noticed an issue.

Vista includes 3.0, 7 includes 3.5, next year 4.0 will be out. 3.5 is a 200MB redist, 4 will be more.

So what? Office 2007 SP2 is 300+MB. The frameworks don't get updated that often.

Microsoft makes operating systems -- environments for other software to run in. They can push the industry forward, or hold the whole industry back.

They are pushing forward by providing the the option of using the newer framework, or letting you stay with the older framework. Developers choice.

PhreePhly
 
Backward's compatibility with software or hardware?

Does it really matter? If their stuff isn't working, they're going to complain. It was usually hardware, and yes, a lot of printer issues.

There were not many software packages that didn't work if you applied the XP compatibility switch. Hardware was different. Every OS release has hardware issues. The vendors wait until after RTM to get drivers out. Vista was in beta for almost 2 years, but nVidia couldn't get a stable driver until 8 months after release. HP still has printers that came out a year or two before Vista and haven't provided a Vista driver to date. Not MS's or the OS's fault.

I have a hard time swallowing the notion that it was simply the hardware vendor's fault, particularly when several major hardware companies (nvidia and HP) products were having driver issues with the OS.


Also, OEM's did a terrible job of putting Vista on proper hardware.

Again, I find it hard to believe that none of the blame goes to microsoft, for developing a bloatware, resource hog of an OS.

UAC is necessary.

no, it's not necessary... giving average users default admin accounts, also, is not necessary.

The general user is stupid. There is no way around that.

Exactly, and that's why UAC is pointless... General users are stupid, and they don't KNOW when to allow a program access or not.. They typically tend to just shrug their shoulders and click "allow", any time it pops up on the screen. These are the same people that think the advertisement on myspace that says "You have 5 new messages! Click here to retrieve them!" = their inbox.

The UAC thing was another bullsh*t media hyped joke.

Couldn't disagree, more.

I don't recall many favorable articles about Vista. It was getting hammered even in the RC stages by the tech rags. It struck me rather odd how badly Vista was being reviewed. I was running it on a 5 year old MB at the time and was having little trouble with it.

I did not see these ragging reviews that you speak of, when vista *first* came out. I followed the development of vista, closely, for years.. set back after set back.. I specifically followed Paul Thurrott's Window's Supersite
,and in his final review of vista, the review largely aligned towards the positive. Believe me, if you read his articles regularly, you know he's not a shoe in for microsoft.




Actually, the newer ways to get to the same old areas require fewer clicks on the whole for an average user and are more plain and clear about what they're for, whereas in XP/2000 it was constant drill-downs. Breaking tabs off into their own section was probably one of the smarter UI moves for Vista. The only other option would have been to put everything into a single integrated preferences table (like OS X), which would have been even more confusing. All in all, in my experience the main group of people who have had a problem with the menu and preference window structure in Vista are the ones who expected it to be like or had gotten used to the convoluted structure of XP.

Couldn't disagree, more. Navigating, and getting to network connections is a nightmare... And this is coming from someone who used to do internet tech support, so i worked with this specific area in vista on a very regular basis.

Oh, and: I'm comfortable calling myself a power user, and the only times I run into UAC are when I install software or am making a configuration change to the system. That's it. The claims about UAC are pretty much bogus. I've even attempted to get people to prove it to me by duplicating the behavior in front of me, and it always falls back to making system changes or installing software.

You've tried to get people to prove it? I do spyware/virus cleaning scripts on Vista computers every day of my work week.. Firstly, this fact is indicative that UAC obviously ISN'T serving it's purpose for the general user, very well.. and for two.. i have to click the UAC at least five times while I'm running my script. It is nothing, but an annoying ornament to me.. and a laughable joke to a great deal of spyware/adware/viruses that confront it.
 
Last edited:
no, it's not necessary... giving average users default admin accounts, also, is not necessary.
Vista default admin account is nothing like XP admin accounts, nor is it equivalent to root. The way they are setup doesn't represent a security problem for the average user.

Exactly, and that's why UAC is pointless... General users are stupid, and they don't KNOW when to allow a program access or not.. They typically tend to just shrug their shoulders and click "allow", any time it pops up on the screen. These are the same people that think the advertisement on myspace that says "You have 5 new messages! Click here to retrieve them!" = their inbox.
Would you make the same comment regarding the unix root/sudo model? That it is pointless because users are stupid and will prefer to always log as root on their box instead of having to call sudo every time they elevate their privilege?

You've tried to get people to prove it? I do spyware/virus cleaning scripts on Vista computers every day of my work week.. Firstly, this fact is indicative that UAC obviously ISN'T serving it's purpose for the general user, very well.. and for two.. i have to click the UAC at least five times while I'm running my script. It is nothing, but an annoying ornament to me.. and a laughable joke to a great deal of spyware/adware/viruses that confront it.
Why don't you just disable UAC before running your script?
 
I did not see these ragging reviews that you speak of, when vista *first* came out. I followed the development of vista, closely, for years.. set back after set back.. I specifically followed Paul Thurrott's Window's Supersite
,and in his final review of vista, the review largely aligned towards the positive. Believe me, if you read his articles regularly, you know he's not a shoe in for microsoft.

Nope, I have to agree with PhreePhly here, because I too recall plenty of belly-aching when Vista first came out. I was using it myself since RC2, and there were 'hacks' for trying to make it more like XP before Vista even went RTM (Nov. 2006). The major issues with Vista at the time of release were the lack of driver support from vendors-- yes, despite what you may think (or have implied), MS can't force nVidia and HP to write drivers for the hardware they put out-- a serious lack of software support from developers (who didn't want to rewrite their software... Roxio was a big offender), and what many considered a hair-trigger with UAC. By the time the first service pack was released, driver support was much better, software developers had begun writing for the newer system, and SP1 loosened the triggers for UAC. Yet now, a year and a half since SP1 was released, I still continue to hear the gripes that applied to when Vista first released, as if nothing has changed from Nov. 2006 to now. Suggesting that little or nothing has changed or that the most common gripes haven't been addressed on Microsoft's side as best as they're allowed-- again, they can't force hardware and software vendors to update their code-- is ignoring way too much for me to take any more seriously than those ridiculous "I'm a Mac" advertisements.



GreNME said:
Actually, the newer ways to get to the same old areas require fewer clicks on the whole for an average user and are more plain and clear about what they're for, whereas in XP/2000 it was constant drill-downs. Breaking tabs off into their own section was probably one of the smarter UI moves for Vista. The only other option would have been to put everything into a single integrated preferences table (like OS X), which would have been even more confusing. All in all, in my experience the main group of people who have had a problem with the menu and preference window structure in Vista are the ones who expected it to be like or had gotten used to the convoluted structure of XP.
Couldn't disagree, more. Navigating, and getting to network connections is a nightmare... And this is coming from someone who used to do internet tech support, so i worked with this specific area in vista on a very regular basis.

You're allowed to disagree with me-- that's fine. It doesn't change the fact that there's very little I can't show the average user how to do that isn't umpteen times easier than showing them on XP. All it takes is specifically not treating Vista like XP in the first place-- a mistake the 'enthusiast' community can often make (they also made it going from 2k to XP). I sympathize with your experience, I really do, but please trust me when I say that I have a few years of supporting users under my belt as well and I'm not just making my claims up from thin air. The main obstacle to finding the easy ways to do things in Vista is the muscle (or action) memory people developed from using XP for 5 years.

GreNME said:
Oh, and: I'm comfortable calling myself a power user, and the only times I run into UAC are when I install software or am making a configuration change to the system. That's it. The claims about UAC are pretty much bogus. I've even attempted to get people to prove it to me by duplicating the behavior in front of me, and it always falls back to making system changes or installing software.
You've tried to get people to prove it? I do spyware/virus cleaning scripts on Vista computers every day of my work week.. Firstly, this fact is indicative that UAC obviously ISN'T serving it's purpose for the general user, very well.. and for two.. i have to click the UAC at least five times while I'm running my script. It is nothing, but an annoying ornament to me.. and a laughable joke to a great deal of spyware/adware/viruses that confront it.

Yeah, I've asked people to repeat the results they are telling me they get-- sure, it's a typical troubleshooting approach, but when it comes to separating hyperbole from reality on things like this issue the approach is highly effective. I've done it before on other issues, such as people claiming running without a page file provides better performance (it doesn't, I tested it) or when QuackViper's service disabling guide was all the rage (again, tested it and found no improved performance, but did lose features), and the most common theme with these widely-used claims is that they sound reasonable in the presentation but either have no effect or can even have adverse effects when actually applied to a real computing environment. But I digress on that point...

You seem to be under the wrong impression about UAC and what it does, what it's for, and how it works. It's not there to stop malware from installing, but it does slow malware down. Unfortunately it's not going to matter if the user is clicking 'Yes' or 'Continue' at every prompt that comes up, which is the number one reason why there are so many problems with malware-- to high of user privs and too little attention paid when prompts pop up. Where UAC is helpful, however, are times when all of the users on the home computer aren't running as admin, or on a business network where UAC gives me greater ability to handle software installs, updates, and configuration changes by essentially giving me a Windows equivalent to sudo that works.
 
Vista default admin account is nothing like XP admin accounts, nor is it equivalent to root. The way they are setup doesn't represent a security problem for the average user.

That's funny, considering I still see loads of security problems for the average Vista user.


Would you make the same comment regarding the unix root/sudo model? That it is pointless because users are stupid and will prefer to always log as root on their box instead of having to call sudo every time they elevate their privilege?

Now you're just getting ridiculous. A) VERY few average users use unix/linux - ADVANCED users do. B) Average users wouldn't even know how to log in as root


Why don't you just disable UAC before running your script?

Policy does not allow us to.

You seem to be under the wrong impression about UAC and what it does, what it's for, and how it works. It's not there to stop malware from installing, but it does slow malware down

I thought UAC was to prevent programs from running without user/admin permissions.. This very obviously seems like a stab at stopping security threats, specifically - malware.
 
I thought UAC was to prevent programs from running without user/admin permissions.. This very obviously seems like a stab at stopping security threats, specifically - malware.

Nope, you're definitely under the wrong impression. ACLs and malware protection software serve that purpose, not UAC. Do you understand what sudo is?
 
Wait a second:
ZouPrime said:
Why don't you just disable UAC before running your script?
Policy does not allow us to.

You mean your policy doesn't allow you to use methods provided by Microsoft to bypass the UAC prompt (i.e.- using Task Scheduler or inlining the admin account)? That sounds a bit ridiculous.
 
My comment, then a minor thread hijack.

Firstly, I still use XP. It's been a reliable and stable system for me. I'm not doing a reformat to load Win7 RC1, nor loading Vista to upgrade to RC1, nor am I going to set up a dual boot. I'll wait... probably until Win7 SP1, I suppose.

Now, on a related note: I was reading an article about the lady in charge of Win7; apparently she was also in charge of Office 2007 and one of the comments in the article was that she steadfastly refused to allow Office 2007 users to use a "classic" Office GUI, and that this was hailed as a successful and popular move.

Do people agree with this? I certainly do not. I remain with Office 2003 because it takes me 5 or 6 times longer to produce anything more than a very basic document in Officer 2007. I was happy and familiar with the locations and procedures to format, make sections, make various paragraphs types, etc. Now I can't find where the commands are and spend an inordinate amount of time trying to do something I previously did in seconds. Other users I have spoken to say the same thing - but it's a very small group I have canvassed.

So - Office 2007 GUI: like or dislike?

Thanks.
 
Does it really matter? If their stuff isn't working, they're going to complain. It was usually hardware, and yes, a lot of printer issues.


I have a hard time swallowing the notion that it was simply the hardware vendor's fault, particularly when several major hardware companies (nvidia and HP) products were having driver issues with the OS.

Too bad, the truth is out there. Why is it that ATi could get their drivers working just fine? Why is it that Epson had no problem writing Vista drivers? nVidia and HP were lazy. Go back and look at Windows 3.1 to Win 95. HP couldn't get drivers working for that transition either. They had the same problem for each major OS upgrade.


Again, I find it hard to believe that none of the blame goes to microsoft, for developing a bloatware, resource hog of an OS.

Now you're just a troll.

no, it's not necessary... giving average users default admin accounts, also, is not necessary.

Admin in Vista still runs with lesser elevation than admin. UAC informs you when a program is requesting elevation.

Exactly, and that's why UAC is pointless... General users are stupid, and they don't KNOW when to allow a program access or not.. They typically tend to just shrug their shoulders and click "allow", any time it pops up on the screen. These are the same people that think the advertisement on myspace that says "You have 5 new messages! Click here to retrieve them!" = their inbox.

At least there is a notification. Not much else you can do.

Couldn't disagree, more.

Disagree all you want.

I did not see these ragging reviews that you speak of, when vista *first* came out. I followed the development of vista, closely, for years.. set back after set back.. I specifically followed Paul Thurrott's Window's Supersite
,and in his final review of vista, the review largely aligned towards the positive. Believe me, if you read his articles regularly, you know he's not a shoe in for microsoft.

He's a hack. The crap he spews isn't taken seriously by anybody.

Couldn't disagree, more. Navigating, and getting to network connections is a nightmare... And this is coming from someone who used to do internet tech support, so i worked with this specific area in vista on a very regular basis.

Just as many clicks as XP. Different screens, same number of clicks.

You've tried to get people to prove it? I do spyware/virus cleaning scripts on Vista computers every day of my work week.. Firstly, this fact is indicative that UAC obviously ISN'T serving it's purpose for the general user, very well.. and for two.. i have to click the UAC at least five times while I'm running my script. It is nothing, but an annoying ornament to me.. and a laughable joke to a great deal of spyware/adware/viruses that confront it.

Then turn UAC off. How about educating your clients? There's only so much you can do for stupid, and no OS can fix that. But you provide tools to inform. That is what UAC does.

PhreePhly
 
My comment, then a minor thread hijack.

Firstly, I still use XP. It's been a reliable and stable system for me. I'm not doing a reformat to load Win7 RC1, nor loading Vista to upgrade to RC1, nor am I going to set up a dual boot. I'll wait... probably until Win7 SP1, I suppose.

Now, on a related note: I was reading an article about the lady in charge of Win7; apparently she was also in charge of Office 2007 and one of the comments in the article was that she steadfastly refused to allow Office 2007 users to use a "classic" Office GUI, and that this was hailed as a successful and popular move.

It's actually a he, and yes, that was the best thing he could of done. First of all, the ribbon is a fabulous interface. Much faster to get to any command as compared to the 1997 - 2003 menu setup.

Do people agree with this? I certainly do not. I remain with Office 2003 because it takes me 5 or 6 times longer to produce anything more than a very basic document in Officer 2007. I was happy and familiar with the locations and procedures to format, make sections, make various paragraphs types, etc. Now I can't find where the commands are and spend an inordinate amount of time trying to do something I previously did in seconds. Other users I have spoken to say the same thing - but it's a very small group I have canvassed.

So - Office 2007 GUI: like or dislike?

Best interface to date. I'm glad they didn't provide an avenue to disable it.

PhreePhly
 
That's funny, considering I still see loads of security problems for the average Vista user.
UAC (nor the sudo/root model) doesn't protect against all possible malware vector, so I don't see your point.

A trojan is going to be destructive on XP, on Vista, or on any OS in the world. That's not what these controls are designed to protect against.



Now you're just getting ridiculous. A) VERY few average users use unix/linux - ADVANCED users do. B) Average users wouldn't even know how to log in as root
I'm not getting ridiculous, you completely missed (or ignored) my point. UAC and sudo/root are designed to protect against non-user initiated privileged escalations. Both controls are useless if the user is stupid and actively seek to install the malware. That's a basic consequence of having user-initiated privileged escalation.

Saying that UAC is pointless is like saying that sudo/root is pointless - of course it's not, and while not perfect, it's perfectly possible to expect the general users to learn how they work as the model ends up being on all workstation-grade OSes in a few years.

Policy does not allow us to.
Tell your local security guy to ask/declare a derogation.

I thought UAC was to prevent programs from running without user/admin permissions.. This very obviously seems like a stab at stopping security threats, specifically - malware.
Some malware, yes. Actually, some propagation vectors. But not all malware and propagation vectors.
 
Nope, you're definitely under the wrong impression. ACLs and malware protection software serve that purpose, not UAC. Do you understand what sudo is?

Yes I do understand what sudo is. You still obviously don't understand the purpose of UAC.

Wait a second:


You mean your policy doesn't allow you to use methods provided by Microsoft to bypass the UAC prompt (i.e.- using Task Scheduler or inlining the admin account)? That sounds a bit ridiculous.

It's not ridiculous. You're just obviously not an employee of a company that specializes in removing malware from Windows products, via remote connections.
 

Back
Top Bottom