Coders Tell Why They’re Avoiding Vista

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Several programmers were interviewed and gave their reasons why they or their companies are not writing applications for Vista. This further supports a survey which reported that fewer than 1 in 12 developers are targeting the beleaguered operating system.

According to data released this spring by migration software vendor AppDNA Ltd., about a fifth of enterprise applications running on XP break when moved straight to Vista, mostly due to pre-XP-era code still lingering in the app. That increases to nearly half for apps migrated from 32-bit XP straight to 64-bit Vista.
 
In other words, Vista's business adoption rate is not quite high enough yet for some devs. And those particular devs can't justify the time or expense of properly coding for Vista, especially X64, yet.
 
Considering, most businesses can't properly code their programs for any platform let alone a single OS I can see this makes perfect sense. Just think of how many, launch day applications/games, you've bought that ever worked properly at launch day.

They are blaming a new OS on their coding flaws though. This is a good move, now if only the people that develop for the 360, Wii, PS3 could blame their coding flaws on a particular platform ;p
 
I love how its Vista's fault that these coders can't even move their product into a 32-bit world yet...
 
Quote: "I can't see targeting something only to Vista when you have XP and Windows 2003 out there in huge numbers," said Dave Noderer, a Microsoft MVP who runs the Florida .Net User Group as well as his own software development firm, Computer Ways Inc. in Deerfield Beach, Fla.

It sounds like more of an unwillingness than an inability of developers to expend time developing apps that are targeted to only Vista users. In light of extremely low adoption of Vista in businesses and comparatively low numbers in personal/home use, you can't blame developers for not wanting to bother. Windows 7 release in the next couple years may make developing apps for Vista even less appealing.

If the market isn't interested in a product, it doesn't make much since to waste time and effort working on something nobody wants or can use.
 
Whatever can be said of Vista, I myself am glad that there is at least some standard for coding that they are trying to enforce... Sure you can run anything on XP, but a poorly coded app (like many ones commonly available) only compromises the stability and longevity of your system, and sometimes can even have incredibly disastrous circumstances (data loss, borked windows installations,etc).

Boo woo, coders... find somebody elses's shoulder to cry on...
 
My excuse as a programmer is that I'm just too lazy and busy. A couple of the major APIs are partially or fully supported in XP, but I've been putting it off for a long time.

It's funny because I don't really believe that the browser will replace desktop apps for a majority of cases, but my time has mostly been diverted to web programming and making apps run in a browser. :p
 
So, basically though, 80% of all XP apps work just fine ran on 32bit Vista. Not too shabby all things considered. How many apps did SP2 for XP break?

And don't forget that vocal choir that says Microsoft needs to start completely over with a ground up OS and chuck all backwards compatibility.

All things considered, it's not easy being Microsoft and trying to please everyone.

I just had an amazing experience putting Vista on my old HP Pavilion, and I was very impressed.
 
I'm having some difficulty getting Visual Studio 2005 the even install properly on Vista Business x64.

I will get it to work however... There are patches... VS 2005 SP1 and VS 2005 SP1 Vista patch.

Really, just like in the article, none of the new "flashy" stuff is needed... just more bloatware if you ask me.

It's kinda freaky how the Windows Mobile 5 and 6 SDKs will NOT install unless you have Visual Studio 2005 or later installed.... and the "express" versions of Visual Studio are not compatible.

I am starting to understand why there isn't a lot of open source or free programs for WM5 or WM6..... MS doesn't want people developing free stuff for the mobile platform.
 
Basically how I read it is that essentially 20% of the enterprise software still utilizes 16-bit code, which XP will still run, but Vista will not. I don't essentially see this as a shortcoming of Vista but more an indicator that companies running enterprise software are still unwilling to replace applications which are a decade old. The day will come where these companies will just have to give up that 16-bit code they are so reluctant to get rid of and recode to 32 or 64-bit to suit the newer hardware and OS needs.
 
120 million users and climbing is hardly a small number for Vista.

Why are people coding for the mac then. lol?
 
I must agree w/ Mubata. It is disgusting that companies just want to lay the blame on MS. MS isn't perfect, but think of how much effort they've put into making a vast array of hardware work on Windows.
 
I guess the only thing I've got to say is why program for Vista when so many users are on XP. Develop a program targeted at Vista when the majority of your user base is on XP? By the time windows 7 rolls around, the majority of your user base will be on Windows Vista, and Windows 7 is sure to have some new cool programming features too. Will you use them even 2 years in? Probably not, but you can bet by that time people will be fully ready to write an aero/DX10/insertvistaonlyfeature capable app.

Look guys Vista is really simple: if you own a machine running XP, don't upgrade, its just not worth it. But if your buying a PC, get vista, because otherwise you really are neutering the capabilities of your box. It is not hard to write a program that functions perfectly across the X64-X86 and Vista-XP field. When windows 7 rolls around XP users will start to be hung out to dry, thats the way this biz works.
 
Only win64 will not run win16 code. It's not vista related at all. XP64 won't run it, Vista32 will.
 
More attractive apps are more user-friendly apps, says Microsoft, and that translates into increased user productivity. But that message remains a hard sell to enterprises, who demand their apps stay "lean and mean," said Krasowski, not get "confused and cluttered."

This proves there needs to be a greater difference between Home Premium and Business. Whats pissed my off about the Vista thing is all the different versions with little difference. Media Center in one build, not the other instead of real performance differences. Users will not notice the difference between Business and Home besides the fact Media Center is there.
 
I guess the only thing I've got to say is why program for Vista when so many users are on XP. Develop a program targeted at Vista when the majority of your user base is on XP? By the time windows 7 rolls around, the majority of your user base will be on Windows Vista, and Windows 7 is sure to have some new cool programming features too. Will you use them even 2 years in? Probably not, but you can bet by that time people will be fully ready to write an aero/DX10/insertvistaonlyfeature capable app.

Look guys Vista is really simple: if you own a machine running XP, don't upgrade, its just not worth it. But if your buying a PC, get vista, because otherwise you really are neutering the capabilities of your box. It is not hard to write a program that functions perfectly across the X64-X86 and Vista-XP field. When windows 7 rolls around XP users will start to be hung out to dry, thats the way this biz works.

You are missing the big picture here. This isn't a "code for Vista" problem, which I can see, this is a "code to 2000/XP standards" issue. Some developers are STILL writing pre-2000 code. God knows why, since the API is downright terrible. Win32 is probably the single stupidest API design I have ever come across. If developers actually coded to the standards MS laid out years ago for XP, there wouldn't be any problems, but they didn't.

And this isn't anything Windows specific. The problem is amplified because of MS's attempts to bend over backwards to maintain compatibility, which meant bad choices and designs never got flushed out of the system. Linux, on the other hand, has a policy where you *DON'T* try to maintain backwards compatibility (binary or source). As such, if something better was designed, it replaced the old, and everyone better fix their code or stay on the old system. Essentially natural selection for software.
 
Quote: "More attractive apps are more user-friendly apps, says Microsoft, and that translates into increased user productivity."

ummm....yeah. I think I see the problem.

What if he said, "Cleaner, simpler and more intuitive apps translate to increased productivity."

Good functioning applications don't need sprinkles and glitter.
 
If developers actually coded to the standards MS laid out years ago for XP,

Not just XP. The 'all software must run as nonadministrator' standard actually dates back at least as far as win2k, if not to NT4/3.5.
 
Not just XP. The 'all software must run as nonadministrator' standard actually dates back at least as far as win2k, if not to NT4/3.5.


That right there would fix one of the biggest complaints regarding Vista that we all hear. "UAC prompts suck." Those would be a far more seldom occurrence if that one little rule was followed.
 
As the inception rate increases for Microsoft Windows Vista, programmers need to get off their collective asses and get their shit in gear. :)
 
Disclaimer: I work for Microsoft, but I'm not part of the Windows group.

I for one am really liking Vista 64. It runs well on my C2Q box (with 8GB of memory) and I haven't had any major compatibility issues.

It seems that most people crapping on Vista don't have any good reason to do so.

People say, "it's slow", but then back it up with benchmarks that show a 5-10% performance difference. Well, considering that my last hardware upgrade provided at least a 2x performance boost, I can't get too worked up about that.

People say, "it needs lots of RAM", which is true. But 2GB DDR2 DIMMS are $30, and that's plenty to run Vista.

People say, "it needs lots of disk space", but my WD6400AAKS was $110 - I'm not going to be too worried that 1/64th of my disk space is used by Vista.

So, I guess, my experience with Vista has been quite good. Yeah, I'm running it on a 2.5GHz quad-Penryn box with 8GB of memory and the fastest 7200rpm drive you can buy. Yeah, I have a fast (Radeon HD 3850) GPU. But, you know what? This hardware isn't really "high end" anymore, it's decidedly midrange. And Vista runs fine on my 2GHz Core 2 Duo / Intel Integrated / 2GB business laptop, too.
 
It seems that most people crapping on Vista don't have any good reason to do so.

People say, "it's slow", ...
Yeah, I agree that most who complain are just parroting 3rd hand information. But some people really are having problems, some things are the fault of the hardware or drivers (or 1337 tweaking), and some things are true Vista annoyances. Then there's the other category of people who hate Vista because it requires them to learn new things, but they're hopeless. :p

My experience is much like yours. Memory is dirt cheap and that's the primary complaint about hardware that is otherwise from the Vista era. Modern hardware runs Vista great, and I'm not talking about high end stuff. I switched to Vista x64 on my main system over a year ago and I haven't regretted it. I can slap together a $300 system that will run Vista well, and most people here spend much more than that on hardware.
 
I can slap together a $300 system that will run Vista well, and most people here spend much more than that on hardware.

Hell, lots of people here spend more than that on a videocard. :)
 
Silly MS bashing article. Pretty well all new programmes for windows are designed to work on vista, but they work on XP too.
You write programmes for your target market, which is now a mixture of Win2k, XP and vista for most applications. Just because all huge corporations haven't instantly switched to vista doesn't mean none are, or won't have when the programme you are writing actually gets released - all new applications have to work on vista or you will loose a lot of sales.
 
Silly MS bashing article. Pretty well all new programmes for windows are designed to work on vista, but they work on XP too.
You write programmes for your target market, which is now a mixture of Win2k, XP and vista for most applications. Just because all huge corporations haven't instantly switched to vista doesn't mean none are, or won't have when the programme you are writing actually gets released - all new applications have to work on vista or you will loose a lot of sales.

AFAIK, Win2000 is under 2.5% of the market, so nowadays, most people don't give two shits about Win2000.
 
Thing is, coders should adapt Vista well before users, because they have to fix their programs so they actually work in Vista by the time Vista becomes the new standard Windows OS (which is inevitable, as XP will eventually be unavailable and all new PCs have to run with Vista... in fact, I don't think I can even install XP on some of my new systems, simply because it has a harddisk controller that is not supported by the XP installation media, and I have no floppy drive, and there is no other way to load drivers during an XP installation... The only alternative would be to make custom slipstreamed images for such systems, but that's just too much hassle... and requires a working system in the first place).

My company is not working on Vista yet, and we are just too late. We should have moved development over to Vista ages ago, and at least iron out the most obvious problems (limited user rights for Program Files, registry etc), and at least do some rudimentary testing.
In a way it's just poor planning... because we are working on a new suite in .NET 2.0, which will work on Vista with little or no problems... it just won't be ready in time. So we're already developing on two fronts... the old XP codebase which is still supported and expanded... and the next-gen .NET suite... We simply don't have the time to freeze development and work on Vista issues, and we don't have the resources to let some people work on finding Vista issues. Nothing I can do about it sadly.
At least I switched to XP x64 and Vista x64 early at home, and most of my code ported very cleanly.
Then I moved on to D3D10.
 
Basically how I read it is that essentially 20% of the enterprise software still utilizes 16-bit code, which XP will still run, but Vista will not. I don't essentially see this as a shortcoming of Vista but more an indicator that companies running enterprise software are still unwilling to replace applications which are a decade old. The day will come where these companies will just have to give up that 16-bit code they are so reluctant to get rid of and recode to 32 or 64-bit to suit the newer hardware and OS needs.

Amen to that Bro.. Try finding modern software in the Process Control and Automation world. Most are just now getting to building XP apps.. Many plans/mills are still running NT4 just to be compatable..
 
Heck, in some places they still use DOS. As long as it works, why spend money on new PCs, new OSes and rewriting the software?
So in a way, trying to remain up-to-date is a very bad decision from a management point-of-view.

The real problem is ofcourse that when they do eventually have to upgrade because their old system broke down or whatever other inevitable failure... they painted themselves in a corner so much that nothing works anymore.
They can't interface their hardware on a new system, they don't have drivers, they can't run the old OS they used to run on their old system, their application can't run on the new system etc.
 
Disclaimer: I work for Microsoft, but I'm not part of the Windows group.

I for one am really liking Vista 64. It runs well on my C2Q box (with 8GB of memory) and I haven't had any major compatibility issues.

It seems that most people crapping on Vista don't have any good reason to do so.

People say, "it's slow", but then back it up with benchmarks that show a 5-10% performance difference. Well, considering that my last hardware upgrade provided at least a 2x performance boost, I can't get too worked up about that.

People say, "it needs lots of RAM", which is true. But 2GB DDR2 DIMMS are $30, and that's plenty to run Vista.

People say, "it needs lots of disk space", but my WD6400AAKS was $110 - I'm not going to be too worried that 1/64th of my disk space is used by Vista.

So, I guess, my experience with Vista has been quite good. Yeah, I'm running it on a 2.5GHz quad-Penryn box with 8GB of memory and the fastest 7200rpm drive you can buy. Yeah, I have a fast (Radeon HD 3850) GPU. But, you know what? This hardware isn't really "high end" anymore, it's decidedly midrange. And Vista runs fine on my 2GHz Core 2 Duo / Intel Integrated / 2GB business laptop, too.

I have vista on my home computer and I have little to no problems with it, certainly no more than I had with xp. I also agree that the hardware requirements for vista are pretty cheap now, although when you're a business with dozens or thousands of systems it's not as easy as throwing in a $30 stick of ram. Any seemingly minimal upgrade cost is multiplied by the number of systems in addition to the wages of whoever is doing the upgrades and lost productivity. That said, this is no different from any other upgrade, and I still don't see what the big deal is with vista or how it's any different from win95>98 or win98>2000.;)
 
Back
Top