I think this is a bad idea, unless they are going to go with things like nspluginwrapper…
Todays computer industry simply isn’t ready for 64bit desktops (which as far as I know is where arch targets).
I think they should consider implementing something like multilib. Arch is known for its speed and simplicity, would be a shame if their 64bit offerings weren’t really relivant for desktop users…
EDIT: Simplicity of design, not necessarily use… just to clear that up…
Todays computer industry simply isn’t ready for 64bit desktops
Just because adobe won’t build 64 bit flash? Geez, there is actually computer industry usage besides youtube. I don’t miss it at all, been months since I’ve had it waste my bandwidth, actually improves the browsing experience.
I’ve been using Arch64 for a few months now (since I got my X2), and I have to say that the “64 or nothing” philosophy seems the most sensible philosophy out there at the moment. 32 bit systems are slowly but surely dying, so postponing the shift from 32bit to 64bit systems is just delaying the inevitable. It’s best to invest effort into fixing and working with 64bit software now, rather than later.
32bit only system are becoming more rare, that’s true but those x86-64 computers will keep their 32-bit mode for a *very long* time.
So there is absolutely no reason to hurry the 32–>64bit transition, sure there is usually a performance increase in 64bit mode due to the increased number of register in x86-64, but it’s small and there can even be a performance decrease due to the increase size of pointers, added padding, etc.
What is sensible is for software producers to make 64bit compatible software now so that they let their user chose which is best, and for the user to stay in 32bit mode until all their software are compatible.
I think this is a bad idea, unless they are going to go with things like nspluginwrapper…
Todays computer industry simply isn’t ready for 64bit desktops (which as far as I know is where arch targets).
I think they should consider implementing something like multilib. Arch is known for its speed and simplicity, would be a shame if their 64bit offerings weren’t really relivant for desktop users…
EDIT: Simplicity of design, not necessarily use… just to clear that up…
Edited 2006-11-29 19:40
I think this is a bad idea, unless they are going to go with things like nspluginwrapper…
From the article:
Arch64 does have the nspluginwrapper ready to go in the community repositories, so you can run flash on a 64bit browser.
Todays computer industry simply isn’t ready for 64bit desktops
Just because adobe won’t build 64 bit flash? Geez, there is actually computer industry usage besides youtube. I don’t miss it at all, been months since I’ve had it waste my bandwidth, actually improves the browsing experience.
I’m a arch user and was searching for a 64bits disto… looks like i’m still going to be in ArchLinux for a while.
I’ve been using Arch64 for a few months now (since I got my X2), and I have to say that the “64 or nothing” philosophy seems the most sensible philosophy out there at the moment. 32 bit systems are slowly but surely dying, so postponing the shift from 32bit to 64bit systems is just delaying the inevitable. It’s best to invest effort into fixing and working with 64bit software now, rather than later.
Sorry but that’s bull.
32bit only system are becoming more rare, that’s true but those x86-64 computers will keep their 32-bit mode for a *very long* time.
So there is absolutely no reason to hurry the 32–>64bit transition, sure there is usually a performance increase in 64bit mode due to the increased number of register in x86-64, but it’s small and there can even be a performance decrease due to the increase size of pointers, added padding, etc.
What is sensible is for software producers to make 64bit compatible software now so that they let their user chose which is best, and for the user to stay in 32bit mode until all their software are compatible.