On Wed, Mar 24, 2010 at 7:35 PM, gushi <email address hidden> wrote:
> On Wed, 24 Mar 2010, Noel J. Bergman wrote:
>
>> The fix is to move directly to the 64 bit version, and stop worrying
>> about nspluginwrapper. How did a 32-bit stopgap become the only and
>> blessed solution?
>
> No official non-alpha-quality x64 bit version from the upstream vendor,
> maybe? And yes, while it's true you are CURRENTLY able to download it
> (even in alpha), that was not the case at the original inception of this
> bug.
So does that mean the bug is grandfathered in because it got here
first? In this case, alpha is just a label, and the 64-bit flash
player is much more stable than running 32-bit flash under
nspluginwrapper, according to many users who have commented on this
thread. There doesn't seem to be any reason to keep the 32-bit flash
plugin under nspluginwrapper that makes up for its brokenness.
On Wed, Mar 24, 2010 at 7:35 PM, gushi <email address hidden> wrote:
> On Wed, 24 Mar 2010, Noel J. Bergman wrote:
>
>> The fix is to move directly to the 64 bit version, and stop worrying
>> about nspluginwrapper. How did a 32-bit stopgap become the only and
>> blessed solution?
>
> No official non-alpha-quality x64 bit version from the upstream vendor,
> maybe? And yes, while it's true you are CURRENTLY able to download it
> (even in alpha), that was not the case at the original inception of this
> bug.
So does that mean the bug is grandfathered in because it got here
first? In this case, alpha is just a label, and the 64-bit flash
player is much more stable than running 32-bit flash under
nspluginwrapper, according to many users who have commented on this
thread. There doesn't seem to be any reason to keep the 32-bit flash
plugin under nspluginwrapper that makes up for its brokenness.