Post by George on Feb 28, 2017 11:15:46 GMT -5
Robert: Thanks for doing this post. Yes, lack of input/feedback has been a problem since way back in the version 1 days (where it was mostly bug reports and "why haven't you implemented the ISPF command xxx?")
As you personally are only too painfully aware, I haven't even tackled a majority of your ideas, I shoot them down. Sometimes because I just don't feel there is any demand for the function, and sometimes because the change is simply way too disruptive to the SPFLite internal code and structure. The latter here is just a fact of life; SPFLite just grew, and grew, and grew. Not always logically, usually in a "whatever is simplest to implement" way. And despite some major clean up / tidy up efforts over the years, we still have 50-60K lines of code, spread over 30+ modules to manage, not an easy task. Especially for someone in their mid-70's who can't remember where he left his reading glasses. ;-)
Input / comments / feedback etc. from the users is essential if we're ever going to do more than patch up reported bugs.
George
As you personally are only too painfully aware, I haven't even tackled a majority of your ideas, I shoot them down. Sometimes because I just don't feel there is any demand for the function, and sometimes because the change is simply way too disruptive to the SPFLite internal code and structure. The latter here is just a fact of life; SPFLite just grew, and grew, and grew. Not always logically, usually in a "whatever is simplest to implement" way. And despite some major clean up / tidy up efforts over the years, we still have 50-60K lines of code, spread over 30+ modules to manage, not an easy task. Especially for someone in their mid-70's who can't remember where he left his reading glasses. ;-)
Input / comments / feedback etc. from the users is essential if we're ever going to do more than patch up reported bugs.
George
