.NET does not promote good code organization
There… I said it!
I’ve been more and more exposed to Java and I really have to say I *love* the constraints that Java puts on you as far as organizing code. Your packages need to follow your folder hierarchy, and one public class per file.
I understand that you can do this with VS.NET as well, however, sometimes when you get in a hurry, its easy to let these things slip by and what you end up with is a big sloppy mess… Unlike Java, it is not enforced at compile time. If I dont keep my code well organized, the compiler fails.
Is it really that hard make the language or framework promote good coding practices and organization?
Booooo. Hisss.
Freedom from the tyranical folder structure contraints of the Java compiler soldiers!
Boooooooooo…..
Sure… Why wouldnt you want to make it easier for the next person to work on your code?
Sure, that would be simple. It would also be simple to enforce coding practices.
But it also probably is just one of the many reasons why Java is shrinking while .NET is exploding everywhere.
Do a job search for .NET vs Java right now. :) .NET pays my bills, how about yours.
Personally I like to organize my code according to the particular order that exists per the job I am working on. That way the “locals” (as I call them) don’t get confused and I just follow their practices.
Last year I went through a reorg of our codebase to follow this structure, and it has made life so much easier when trying to find things in common namespaces, as my folder structure follows my namespace structure.
