News for hackers. Stuff that matters.
Re:32-bit x86 Position Independent Code – It's That Bad by zzzcpan on Wednesday April 15, 2015 @07:34AM (#9380200)
There are no problems with updates anymore. You don't have to download everything to update a bunch of static binaries. There are things, like bsdiff, that allow you to download and patch only tiny differences related to a security flaw.

There is no need for dynamic linking for updates. Really.

Re:32-bit x86 Position Independent Code – It's That Bad by _yosefk on Wednesday April 15, 2015 @07:40AM (#9380226)
What if you have binaries compiled from proprietary code bases from umpteen vendors using different compilers and compiler options and what-not, and they all use the Internet for self-updating and stuff and they all need to be patched? How are you going to do that?

Also - weakly related - what if you want to use a plugin from vendor A inside the program of vendor B, and they live in the same address space - how are you doing it without dynamic loading?

Re:32-bit x86 Position Independent Code – It's That Bad by FreezerburnV on Wednesday April 15, 2015 @09:03AM (#9380652)
Chances are, if you're using those binaries, they have their own versions of whatever libraries they depend on already baked into themselves somehow. So even if they depend on OpenSSL, and you update OpenSSL on your system, they're probably still going to end up using a version from a year ago regardless of what you do.
Re:32-bit x86 Position Independent Code – It's That Bad by kryptiskt on Wednesday April 15, 2015 @09:54AM (#9380943)
> What if you have binaries compiled from proprietary code bases from umpteen vendors using different compilers and compiler options and what-not, and they all use the Internet for self-updating and stuff and they all need to be patched? How are you going to do that?

The proprietary code isn't going to chance using system libs beyond libc, because of portability. So they likely still need to be patched separately.

Re:32-bit x86 Position Independent Code – It's That Bad by wtbob on Wednesday April 15, 2015 @08:04AM (#9380325)
> What if you have binaries compiled from proprietary code bases…

Then don't do that. Seriously, RMS, ESR and others have written a plethora of well-reasoned essays indicating why proprietary software is a poor choice.

Re:32-bit x86 Position Independent Code – It's That Bad by eropple on Wednesday April 15, 2015 @09:52AM (#9380930)
So you're admitting that this isn't a solution and you need to change the rules of the game to make it work.

Well, I'm convinced.

Re:32-bit x86 Position Independent Code – It's That Bad by wtbob on Thursday April 16, 2015 @07:06AM (#9387068)
'Doctor, it hurts when I stab myself in the eye!'

'Well, don't stab yourself in the eye.'

Re:32-bit x86 Position Independent Code – It's That Bad by GFK_of_xmaspast on Wednesday April 15, 2015 @09:15AM (#9380713)
ESR advocating for something is reason enough to seriously consider the alternative.
Re:32-bit x86 Position Independent Code – It's That Bad by zzzcpan on Wednesday April 15, 2015 @07:52AM (#9380260)
I don't see a problem with proprietary code bases.