<div class="gmail_quote">On Thu, Jun 18, 2009 at 11:37 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Are people really still afraid of 64-bit? I've had my head in the sand<br>with respect to this list for, well, a while... But my myth backend<br>
has been running a 64-bit install for nearly four years now, if memory<br>serves. My primary frontend has been 64-bit for around three years off<br>and on (was a 32-bit Mac Mini for a while, currently a 64-bit Dell<br>Studio Hybrid, with a high probability of being replaced by something<br>
that is 64-bit and nVidia graphics sooner than later...). Not to<br>mention my workstations at home and at the office, as well as my laptop<br>that are all running a 64-bit install.<br></blockquote>
<div>Some of us! I run my backend using Fedora 64-bit - because I wanted transcoding speed, stability and memory. I compile myth myself for the backend.</div>
<div> </div>
<div>My frontends all run Ubuntu 32-bit- because it was just that much easier to get some of the av-stuff going a while back (like Adobe Flash, codec-support, alsa, etc), and I use packaged (JY's ) versions of myth. The benefits of ease-of-use outweighed the (perceived) hassle.</div>
<div> </div>
<div>So - a mixed house based on my need/hassle trade-off. Maybe it's time to reassess some of those trade-offs.</div></div>