MobileRead Forums - View Single Post - Why Does Adobe Reader Need a System Restart?

brecklundin · 10-08-2010, 06:51 AM

part of the problem is you are dealing with legacy code...a LOT of legacy code. If coded correctly even in the case of shared DLL's the app should run in it's own memory space so a system restart should never been needed, only the service or app restarted.

Adobe is not alone in this crap...they are too cheap and lazy to recode the whole bloated mess even at the rates they are paying the exploited developers in whatever backwater country they pawn the development off to...trust me none of these companies use top tier developers anymore. If you watch the movie "Outsourced" you get a mildly humorous but also telling look at how people are treated. You know it's bad when call centers/code monkey's or whatever are off-shored from India where they get around an 8-10 to 1 cost per US developer over to China or other Asian country where they are getting 20-25 developers/support staff to one in the US or other country...and notice few if ANY of these jobs end up in the EU either...they head to wherever there are essentially no employee protection laws on the books. Just pay the bribes...errrr....fees and you have a building full of staff and who cares if it's done right. And it's not the poor employee's fault as rarely are they give other than basic training by someone who is likely only going through the motions while in the death-throws of their career and just wants them to reach the minimum level of efficiency....

Hence bloated crappy code from the corporate giants who have all the money to push the right buttons...one day this is going to collapse but I am gonna be long dead before then, unless it happens within the next 3-5 years that is...I would LOVE to see everything collapse under it's own weight of corruption...it will be very ugly and people will die, but we get the world we want it seems...

Now does that make sense? The marketing spin is it's because of the shared DLL thing, but that has not been a real issue since Win98...except for legacy code that never was written to the published Windows application guidelines to begin with...all that should be needed is to restart a process...and yes I have my tin foil hat but that also does not mean I am wrong.

10-08-2010, 06:51 AM	#10
brecklundin Banned Posts: 1,906 Karma: 15348 Join Date: Jun 2007 Device: mine	part of the problem is you are dealing with legacy code...a LOT of legacy code. If coded correctly even in the case of shared DLL's the app should run in it's own memory space so a system restart should never been needed, only the service or app restarted. Adobe is not alone in this crap...they are too cheap and lazy to recode the whole bloated mess even at the rates they are paying the exploited developers in whatever backwater country they pawn the development off to...trust me none of these companies use top tier developers anymore. If you watch the movie "Outsourced" you get a mildly humorous but also telling look at how people are treated. You know it's bad when call centers/code monkey's or whatever are off-shored from India where they get around an 8-10 to 1 cost per US developer over to China or other Asian country where they are getting 20-25 developers/support staff to one in the US or other country...and notice few if ANY of these jobs end up in the EU either...they head to wherever there are essentially no employee protection laws on the books. Just pay the bribes...errrr....fees and you have a building full of staff and who cares if it's done right. And it's not the poor employee's fault as rarely are they give other than basic training by someone who is likely only going through the motions while in the death-throws of their career and just wants them to reach the minimum level of efficiency.... Hence bloated crappy code from the corporate giants who have all the money to push the right buttons...one day this is going to collapse but I am gonna be long dead before then, unless it happens within the next 3-5 years that is...I would LOVE to see everything collapse under it's own weight of corruption...it will be very ugly and people will die, but we get the world we want it seems... Now does that make sense? The marketing spin is it's because of the shared DLL thing, but that has not been a real issue since Win98...except for legacy code that never was written to the published Windows application guidelines to begin with...all that should be needed is to restart a process...and yes I have my tin foil hat but that also does not mean I am wrong.