I like to think I fall into this category - of people who get 64 bit versions when possible.
What I want to know when deciding is that the 32 bit is stable - and the the 64 bit is variable. Then I can decide if I want stability - I choose the 32 bit version, or I want the expanded memory space but it might not work - then I will get the 64 as well.
The most important thing is to know is that the 64bit is not as reliable. Then I can make a choice.
Calling it Beta, or non-official, or experimental (if its largely untested) is a useful way to describe it. IMHO the specifics (only if available) are useful to look up to see what kind of trouble I might get into, but the label is most important.
Cheers...
On 7/20/2014 5:49 PM, Bryce Harrington wrote:
On Sat, Jul 19, 2014 at 12:32:20PM -0700, Josh Andler wrote:
The 64-bit builds should really be considered "beta" at this point, which is why we didn't hold off announcing the release for them. The testing on them is minimal at best and it is a new architecture (for us, on windows) with the potential for it's own quirks which we aren't yet aware of. It's difficult for us to say something is a recommended "stable" release if it's really not as mature as the other releases we have available. So, while users may just see 64-bit or 32-bit, they would likely want to know that one is less tested.
I totally agree with all your points, and you're 100% right. That said... I notice the 64-bit windows builds are quite popular. I hazard to bet that a lot of Windows users are going to be looking for 64-bit specifically and either not understand or not care about the potential quality differences between it and the 32-bit build.
But I'm not sure that leaving them to be provided unofficially 3rd-hand is necessarily the ideal solution either, largely for reasons Brynn highlighted. Is there a way we could provide them but labeled in big red letters that it's untested, experimental, or etc.? So if they grab the 64-bit version and find it too buggy, that they don't just assume this is a buggy release but instead go and try the 32-bit version?
Bryce
Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4716 / Virus Database: 3986/7886 - Release Date: 07/20/14