[Info-vax] Shared Objects And DLL Hell
Kerry Main
kemain.nospam at gmail.com
Thu Jun 30 20:31:34 EDT 2016
> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf Of
> lawrencedo99--- via Info-vax
> Sent: 30-Jun-16 6:47 PM
> To: info-vax at rbnsn.com
> Cc: lawrencedo99 at gmail.com
> Subject: Re: [Info-vax] Shared Objects And DLL Hell
>
> On Friday, July 1, 2016 at 3:07:20 AM UTC+12, Stephen Hoffman wrote:
>
> > DLL Hell is a solved problem. Has been for many years. Apps are
> > adopting the available solutions, too. Slowly.
> >
> > Have a look at .NET, and with the way that applications now deploy
> with
> > the expected frameworks, and with how applications are increasingly
> > bundled together and don't need to splatter their giblets around a
> > system. Or how the applications are prohibited from that.
>
> Windows Dotnet has been around since about 2001, hasn’t it? So
> “slowly” is a bit of an understatement.
>
Let's not forget the OS culture issue here with both Windows & perhaps
to a somewhat lesser degree, Linux as well.
How many new Windows / Linux projects start with the assumption that
their target platform is an existing server running other groups apps?
Following .Net standards would require different App groups to develop
their App standards strategy by actually working together.
In this culture, even with higher mgmt. , monitoring and security costs
associated with VM sprawl, It is just culturally (read politically) easier to
simply give each group their own VM or even physical server.
Heck, in many cases, it is easier to give each developer their own VM.
[snip...]
Regards,
Kerry Main
Kerry dot main at starkgaming dot com
More information about the Info-vax
mailing list