Linked by Howard Fosdick on Sat 24th Nov 2012 17:52 UTC
Thread beginning with comment 543135
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by lucas_maximus O2003
by jabbotts on Mon 26th Nov 2012 18:18
in reply to "RE: Comment by lucas_maximus"




Member since:
2011-01-28
lucas_maximus,
"I still have VB6 apps that work perfectly well."
Funny, I still have nightmares from vb6 active-x hell.
For the most part I think backwards compatibility for *userspace* code in windows is remarkably stable, especially given the 64bit transition. It's not perfect though, and old things are breaking. I was at a shop that was heavily invested in vb6 & activex for numerous products. One of my roles involved deploying these on new platforms, and they definitely encountered numerous incompatibilities, incurring high maintenance costs.
As a side note: citrix is workaround many of the compatibility problems we encountered, albeit at some expense.
"NET has been solid since version 2"
.net apps are not without occasional problems either, sometimes they install on one system but not another (ie when both are winxp3). I gave up installing one .net app on a new win7 home computer even, but I never solved the problem (probably a localised issue).
"While there is nothing wrong with Open source stuff, why move your existing and working code for the sake of it?"
That's just it though, I wouldn't ask people to convert for no reason. If something works, then great (no sarcasm here). But when old things start breaking, regardless of who's at fault, it may be worth looking around at what else exists and pre-emptively avoid another proprietary locked in solution.