sv3tli0, thank you for the reply. It isn't serious and I assure you I am not angry
The trouble I have, and just wanted to voice, is that this is something that brings very little to the table and yet nearly the only thing that breaks backward compatibility (other than the session table). I agree it is not a serious thing so why enforce it and break things instead of merely suggest it as a best practice? One of the things I love about CI is that there are very few 'rules' and you can make things the way you need them to be. This particular rule brings nothing but a breaking change. My own standards for filenaming, which I have used without trouble for years and across platforms and languages, is suddenly not acceptable and for absolutely no reason. We programmers are not babies and we don't need the framework that was simple, light and carried very few restrictions to suddenly start holding our hands and patting our heads.
