>>If there´s an advantage of making Dolphin to be included with an installer, here it is:
>>1- Most times, self-extracting files get damaged. It can be when being packed or when the final user extracts them.
>I'd have to disagree here because I find that this happens to me rarely, and usually only because they were damaged when they were getting packed.
I gotta agree here, I've never heard of breakage with self-extracting files for software. DJBarry does occasionally provide information that I find questionable. (Plus he uses backticks as apostrophes, wtf.)
>>2- The installer provides some dynamic libraries (DLLs, that´s it) that some times can´t be detected after the self-extract, and even some files that are missing in your OS in order to run Dolphin correctly.
>Perhaps, but personally, I'd rather get OS related stuff from the original source.
Missing/incorrect DLLs has been a long-standing issue with Dolphin among less-intelligent users. It's cool that *you're* smart enough to figure out that you need to install the 64-bit version of the VS2010/13 distributable for Dolphin to run on 64-bit Windows, but for every one of you there's four thousand other users who just toss random DLLs into their System32 folders and then wonder why they're getting 0xc000007b errors on 64-bit Dolphin builds and just sigh and keep using the slower 32-bit builds. See the slightly-outdated FAQ for more info: https://dolphin-emu.org/docs/faq/#which-version-dolphin-should-i-download Nowadays all the libs are just included with every download (either via system-affecting installers for stable builds or just plain DLLs-within-Dolphin's-sandbox for the dev builds), so this is rarely an issue.
tl;dr, you have to make accommodations for all the dumbasses that'll inevitably be using your software, whether the advanced users like it or not.
>>1- Most times, self-extracting files get damaged. It can be when being packed or when the final user extracts them.
>I'd have to disagree here because I find that this happens to me rarely, and usually only because they were damaged when they were getting packed.
I gotta agree here, I've never heard of breakage with self-extracting files for software. DJBarry does occasionally provide information that I find questionable. (Plus he uses backticks as apostrophes, wtf.)
>>2- The installer provides some dynamic libraries (DLLs, that´s it) that some times can´t be detected after the self-extract, and even some files that are missing in your OS in order to run Dolphin correctly.
>Perhaps, but personally, I'd rather get OS related stuff from the original source.
Missing/incorrect DLLs has been a long-standing issue with Dolphin among less-intelligent users. It's cool that *you're* smart enough to figure out that you need to install the 64-bit version of the VS2010/13 distributable for Dolphin to run on 64-bit Windows, but for every one of you there's four thousand other users who just toss random DLLs into their System32 folders and then wonder why they're getting 0xc000007b errors on 64-bit Dolphin builds and just sigh and keep using the slower 32-bit builds. See the slightly-outdated FAQ for more info: https://dolphin-emu.org/docs/faq/#which-version-dolphin-should-i-download Nowadays all the libs are just included with every download (either via system-affecting installers for stable builds or just plain DLLs-within-Dolphin's-sandbox for the dev builds), so this is rarely an issue.
tl;dr, you have to make accommodations for all the dumbasses that'll inevitably be using your software, whether the advanced users like it or not.
<@skid_au> fishing resort is still broken: http://i.imgur.com/dvPiQKg.png
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)
<@neobrain> dafuq
<+JMC47> no dude, you're just holding the postcard upside down
----------------------------------------
<@Lioncash> pauldachz in charge of shitposting :^)