Operator overload would be nice.
But I don't think declaring variables whose type can be inferred from the right side of the attribution, semicolons or parentheses for parameterless methods are the biggest problems with Java.
Eclipse launches new language to cut down Java boilerplate - Extend
61–70 of 229 posts
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#62I'm sorry to say, but I think the Go programming language has just been owned by this Extend programming language for Java. Go missed the boat when it did not include some minimum class support to appease the developers used to Java, C++, and so on.
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#63How do I make it work with mvn?
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#64I'm sorry to say, but I think the Go programming language has just been owned by this Extend programming language for Java. Go missed the boat when it did not include some minimum class support to appease the developers used to Java, C++, and so on.
I develop with Eclipse and MDD at my day job, Go in my side projects. I'll definitely evaluate Extend for the day job enterprisey stuff, but in Go, I don't miss the class hierarchy at all; I find it very refreshing.
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#65Parenthesis for method invocations are optional, if the method does not take any arguments. obj.compute instead of obj.compute() That seems silly. The optional semicolons also irritate me. ----------------- (Added) I imagine a committee of Java developers, in a penthouse boardroom at Oracle, meeting with management to discuss Java's descent into disuse. "Lets make Java more concise," suggests a senior developer. "Yes…
There is nothing wrong with optional semi-colons. In most cases, the parser doesn't need them, and the programmer doesn't want to type them. But they're useful in some cases for disambiguation, especially in a language like Xtend that doesn't use an explicit return. E.g. foo("bar") ; (a + b) The semicolon is necessary for disambiguation in a case like this, but there is no reason to require the programmer to put in s…
"The semicolon is necessary for disambiguation in a case like this..."
This is why semicolons should be mandatory or illegal. The whole "optional semicolon" thing is a mis-feature designed by language committees that can't make a decision. One's codebase becomes a mismash of lines with and lines without semicolons, sprinkled in as magic to make the compiler happy.
There are plenty of interesting language features which are useful -- support for "optional semicolons" isn't one of them. The feature needs to die, and people should just choose to use a language that suits their need to type -- or not type -- a ';'.
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#66So, "Extend is for the Java Programmer". I'm curious to see how this will turn out as there are some pretty cool features in this language. (Particularly the multiple dispatch, closures and type inference). However, any Java programmers could have made the switch to Clojure or Scala to keep working with the JVM. But, Extend is different in that it generates Java code instead of JVM. So, I'm wondering who will use tha…
" However, any Java programmers could have made the switch to Clojure or Scala to keep working with the JVM" Clojure is a nonstarter for the vast majority of Java programmers for obvious reasons, and Scala has a perception problem.
> for obvious reasons
As someone from outside the Java universe, I'd like to learn more about those reasons and why they are obvious.
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#67Operator overload would be nice. But I don't think declaring variables whose type can be inferred from the right side of the attribution, semicolons or parentheses for parameterless methods are the biggest problems with Java.
Isn't that restricted by the JVM?
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#68okay folks..
Quick explanation..
Its a text based java dsl..so in other words I could develop in xtend an android application model that covers my dev use cases and than have an Eclipse plugin that is for that model.
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#69Earlier quoted context omitted.
" However, any Java programmers could have made the switch to Clojure or Scala to keep working with the JVM" Clojure is a nonstarter for the vast majority of Java programmers for obvious reasons, and Scala has a perception problem.
> for obvious reasons As someone from outside the Java universe, I'd like to learn more about those reasons and why they are obvious.
I'd wager Clojure and its Lispy roots is way too foreign-looking for most Java programmers. And to be honest, the functional programming paradigm is pretty hard to grasp when you've never seen it before, and requires some effort to get proficient in (and more thought, but I don't want to be derogatory against Java programmers).
Re: Eclipse launches new language to cut down Java boilerplate - Extend
#70Earlier quoted context omitted.
" However, any Java programmers could have made the switch to Clojure or Scala to keep working with the JVM" Clojure is a nonstarter for the vast majority of Java programmers for obvious reasons, and Scala has a perception problem.
> for obvious reasons As someone from outside the Java universe, I'd like to learn more about those reasons and why they are obvious.
The vast majority of Java developers are very, very comfortable with static typing and the most advanced IDEs in software development.
Clojure with its s-expressions and dynamic typing is going nowhere except for some small, high-brow teams...just the way it is.
Scala lost its opportunity a while back with its perception problem and lack of IDE support.