Some thingsBetter living through biologically-inspired optimization More whining about JavaWhy do Java projects always have such deep, complex directory structures? If you have a 200-SLOC web project that I just want to skim the code of to get a feel for how your framework/library works in practice, please don't make me do deep sea diving in my file management program just to look at your autogenerated-getter-and-setter-method heavy .java files. And using Java after using Lisps, Python, and Ruby would never stop being painful: you don't get the efficiency of C++ but you do get the typing headaches. Claim: correct, maintainable, brief, explicit code is more appropriate for an "enterprise" than verbose, mediocre Java code. Add a commentyou're not logged in |