This is about "target < source"; talk about changing the JDK version
obfuscates the point. Changing JDK version is not available to many
(most?) (just guessing).
The only technical points against (that have registered with me, and not
saying that I fully agree with them, and there may be more) are
- hard/confusing to separate language/API
- difficult to support (nb-javac hell is an example)
Why "target < source" is important is discussed in the message that
started this thread and uses Kotlin as an example, and mentions some
important points about frgaal
- Kotlin language quickly evolves and still can be used to generate JDK8
code is a huge benefit
- frgaal language specification independent of the JDK
- frgaal compiler version specified as part of project build script
- frgaal is a member of the javac family
- easy to drop frgaal after switching to newest JDK
Here are some key issues to consider
- How useful is frgaal for NB/java user community? Makes NB more attractive?
- What are the risks? (remember nb-javac hell)
- What are the problems? (language vs API)
As I've been getting deeper into this issue, I wonder why javac does not
support this. Maybe marketing decision or test matrix? Since Oracle is
involved, I'd guess marketing.
BTW, for command line use, I have an alias, use it like javac
frgaal is aliased to
`mvn-repo/org/frgaal/compiler/19.0.0/compiler-19.0.0.jar'
-ernie
On 10/5/22 10:47 AM, Jaroslav Tulach wrote:
Hi.
Recently I brought [Frgaal retrofit compiler](http://frgaal.org) to your
attention again. There was a [PR-4682](https://github.com/apache/netbeans/
pull/4682) and then a discussion in the thread about (not) supporting ecj in
NetBeans: https://lists.apache.org/list.html?dev@netbeans.apache.org - thank
you for your comments.
It all boils down to a simple question: Shall NetBeans try to improve
shortcomings of the JDK?
I have recently given a talk [Forget/Ignore Kotlin, use Java19](https://
www.youtube.com/watch?v=ua-8ySwFgqg). There is a slide describing the benefits
of Kotlin around 5th minute. Clearly the fact that the Kotlin language quickly
evolves and still can be used to generate JDK8 code is a huge benefit.
Frgaal (described around 25 minute) can do the same. It has been modeled to
mimic the Kotlin model:
- language specification independent of the JDK
- compiler version specified as part of project build script
Moreover Frgaal is 100% compatible with future Java language specification -
easy to drop it after switching to newest JDK. Overall it is way easier to
adopt latest Java thru Frgaal than trying to switch to a completely new
language. Why do I have to explain it again and again?
NetBeans can support Frgaal without any problems as it is also (just like nb-
javac) a member of the Javac family. All these compilers generate exactly the
same errors and provide the same WYSIWYG experience. Same errors in the IDE,
same on the command line, same on the CI.
All that is needed is: We have to realize that "innovation happens elsewhere"
and make Java better than the one produced by the JDK team!
Anyone has guts to follow better-than-JDK vision? Then let me integrate Frgaal
into NetBeans and bring the latest Java language features to users of older
JDKs.
-jt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
