Admittedly, we haven't done a very good job at keeping up with the needs of our new users. For a long time, the majority of our users were experienced developers and software systems problem solvers, many of whom actually enjoyed working through the tool installation process and viewed it somewhat as a pre-req for custom pinball software development. Lately, with the increased awareness of the P-ROC and high level software frameworks like pyprocgame and MPF, more casual users are getting into custom pinball development. The associated shift we're seeing in user expectations is clearly something I haven't managed very well.
Relative to libpinproc, pypinproc, and pyprocgame, Windows has never been considered any more or less important than OS X and Linux. The process has been the same in all cases (download the github repo, compile and install the libraries, and develop pinball apps). The difference is that installing and using the build tools and dealing with 32-bit vs 64-bit architectures has proven to be much more difficult in Windows than in Linux (and in OS X up until the last year or so). I personally don't own a Windows machine, though for a couple of years I tested the tools in a Windows VM and distributed a libpinproc/pypinproc installer tool with pre-built binaries.
Regarding the recently discovered issue with initial switch state reading with libpinproc master, please accept my apologies. We have many P3-ROC users, many of whom have been P-ROC customers since the early days and are comfortable working with the libpinproc dev branch. That it's been so long since the dev branch was merged into master is entirely my fault. Yesterday was the first time I heard about anybody having issues with reading initial switch states with the P3-ROC and libpinproc master, and I identified the problem immediately and proposed a work-around. We're now working on getting the dev branch tested so we can officially move the feature(s) over to master.
Given the amount of frustration users are having due to the Windows installation process, a number of us got together today to discuss ways of making the process easy. Instead of going into the details, I'll just say that we hear you, we're working on it, and we expect to have a good solution. In the (hopefully short) meantime, the source code is (and will remain) open and free, and it can be installed manually for those willing to work through the process.
We're here, we're listening, and we want to improve the process. We're also human and time-slicing free software tool development and support with other jobs and activities. The amazing efforts of a lot of people have gotten us where we are today, and we continue to need their help in moving forward.