mystran wrote:Either way, my best guess is that for about 95% of all plugins it's a simple matter of adding another build configuration.
I wasn't really asking for an explanation, I am a dev, just not a dev who sells software plugins, rather I was just explaining that no matter how small the costs are, there are costs. Moreover, sometimes just adding another build configuration is trivial, sometimes it leads you down a rosey path of pain.
If there are devs that choose not to do this then you have examples of devs who have chosen that whatever the actual costs are, they are deemed not worth the additional sales.
I seem to recall that the recent Phasis by NI is only 64 bit. So there you go, there's one concrete example of a dev who has chosen not to bother with 32 bit for a particular plugin. Could be any number of technical reasons, but, it also might be that people who still need 32 bit have a greater tendency of using outdated hardware and, consequently, cause more support problems.
In other words, it may not be a technical reason at all that devs choose to go 64 bit only, perhaps they don't want those customers still on 32 bit because they simply cost too much.
In any case, there's an example and if the development and testing costs are so low then you still have to answer the question as to why NI has chosen not to build for 32 bits? To be clear, I'm trying to answer the question that this thread is posing, not making the case one way or another. I'm not confused by it and I don't give a shit. Other people, however, seem to be confused and think that it's obvious that the N customers who want 32 bit are worth whatever K hours it takes to accommodate them. By example, clearly that's not true.
Also, in my experience, anytime some begins a development statement with "all that you have to do is", then that's seldom "all that you have to do." If you are providing installers you now have to either provide a separate installer or you have to include the 32 bit install paths. If you have documentation and websites, they all have to be updated. If you weren't providing 32 bit before you now have to add this language, if you still aren't providing 32 bit from some things then you have to make this clear.
I also think that it complicates support by adding an additional dimension, and this is something that customers can get wrong. Clearly, NI knows how to build software, so, if it were just "adding another build configuration", they probably would have done that.
The more complication and variation that there is, the more everything about supporting customers costs. Eliminating a potential vector for customer problems for the majority of your customers, e.g., their 64 bit plugin isn't working because they installed it to the wrong place by mistake when choosing paths for 32/64, may be worth more than the few extra customers that you get by including 32 bit.
Bottom line, it's almost certainly a business decision that is far more complex and nuanced than just "add another build configuration."
Last edited by ghettosynth on Mon Jan 15, 2018 1:23 am, edited 1 time in total.