On Thu, Oct 14, 2010 at 2:43 AM, Casper Bang <[email protected]> wrote: > Then have you also noticed, that newspaper articles are among the > hardest to read for kids learning?
Pretty sure this has to do with more than just the number of characters/words. :) > We're all different, but I find the opposite from you applies to > myself. My brain wants to scan and break source up into chunks of > isolated semantic. To that effect, I also tend to write one liners > when I can - I have no need to expose temporary mutable variables into > the scope. > > Source code should be about the smoothest transfer of an AST (the > compiler doesn't care how it's fed this) into my brain. Having to > parse statement with multiple double-nests, is counter-productive to > this goal. I think having to make sure that the human can parse the raw Java AST is the fallacy here. Further, this is particularly why DSLs have gotten to be so popular. The AST is 100% necessary for the conversation between the developer and the computer. For the developer to the developer, it often gets in the way. > Java is not exactly the most succinct language and monitors are dirt > cheap. We could go a long way with a smart IDE handling line-wrapping, > something hopefully we shall have in NetBeans 7. I think line-wrapping could be a pipe-dream here. The problem is more than just "this should be on the next line." There are consideration of what to keep together without destroying white space. With emails and such, line-wrapping works because the fundamental unit is a paragraph, not a character or "node." More directly put, developers haven't even come up with a way that we can agree line-wrapping works in code, how do you plan to codify it? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
