What I want to see after these languages mature a bit is what they have taken away. What complexity from Java have they removed, and what best practices have they enforced? This is one reason Java was powerful -- there were fewer ways to do things, and especially fewer ways to get them wrong.
I want to see a language built with simplicity, clarity, and restraint in mind. Power in a few characters means nothing to me. Pat. On Dec 21, 1:11 pm, Cédric Beust ♔ <[email protected]> wrote: > On Wed, Dec 21, 2011 at 11:03 AM, Kevin Wright > <[email protected]>wrote: > > > For anyone used to Scala, the descriptions of Kotlin and Ceylon are once > > again evoking that same eerie sense of familiarity and the same fears as to > > why anyone would want to clone a feature set so closely. Instead of > > contributing to the pre-existing open source solution. > > There are millions of good reasons for rolling your own thing instead of > contributing to something that already exists (license, dislike for the > original solution's design or implementation, starting something from > scratch, creating your own project, going in for the challenge, learning, > etc...), but ignoring this aspect and going back to your original point, C# > is a good example of something that started as a clone and which later > evolved into something very popular. > > I just find the angle "Why did you invent your own thing instead of adding > to the existing?" very short-sighted and detrimental to research and > discovery, and it usually tells me that the person asking this question has > become a little too comfortable with what he likes and closed-minded to > what he doesn't know he might end up liking too. > > -- > Cedric -- 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.
