septillion: And true, but I merely meant to say that two extension-less tabs is no different then one .ino. All that just happens after the stitching and happens to a single .ino as well.
I actually like automated prototype generation. I'm quite capable of writing by own and do when I want default parameter values but otherwise I find it tedious to write them and maintain them. I'd much rather let the computer do that sort of thing as long as it can get it right most of the time and the recent versions of the Arduino IDE do.
The reasonable argument against multiple .ino files in a sketch that I've heard is that you don't have arbitrary control over what order they are concatenated. I get around that by prepending some characters to the start of the filename so I can control the alphabetical order and thus the order of concatenation. Works fine for me.
All that rubs some people the wrong way and it seems like ninja2 might fall into that camp. I think it might depend on how much people are used to writing code in the standard C/C++ manner. I learned C++ from Arduino so I don't mind doing things the Arduino way but it's great that we have the option to write code to our preference so everyone can be happy.