You want a concurrency meme to dictate language readability? Does foo.getX() guarantee immutability? Does foo.x += 1 exclude it?
/Casper On 9 Aug., 17:03, Viktor Klang <[email protected]> wrote: > On Sun, Aug 9, 2009 at 5:13 AM, John Ament <[email protected]> wrote: > > > My thoughts on the article can be surmised in this one statement > > > foo.x += 1 is so much more readable than foo.setX(foo.getX() + 1) > > Mutable? :( > > > > > > > it's honest and true. so far i've only had to develop a few small > > apps in C# (a couple desktop apps and a couple of server side apps), > > so I definitely don't have a strong feeling of the language (only one > > app was database driven). C# just feels much more like a modern > > programming language compared to java. the one thing the author > > doesn't point out is the ability to declare a class across multiple > > files, this is extremely useful when building desktop applications, as > > you can create one class w/ both UI interaction and back end > > interaction, while keeping the two areas completely separate. > > > i love java, don't get me wrong. started in highschool about 99 and > > have been toying with it since... and as i just typed that i realize > > that i've been tinkering with it for far too long, 10 years now. > > > - John > > -- > Viktor Klang > > Rogue Scala-head > > Blog: klangism.blogspot.com > Twttr: viktorklang --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
