+1 > > No, it's keeping ancient code that works kludged into a system that > desperately wants to move on. > The one line "if" isn't the problem, it's making sure the code in the body > of that if and the code in the "else" coexisting without problems. > > Let's face it, the "code that already works" is NetBeans 17. The "if" is > simple. IF you want to run on JDK 8, use NetBeans 17. > There has yet to be any justification presented to keep future versions > working on JDK 8. Why should we be writing software for over 6 years ago > instead of software for today and tomorrow?
- Re: Lets talk about JDK 8 (new year edition) Jaroslav Tulach
- Re: Lets talk about JDK 8 (new year edition) Michael Bien
- Re: Lets talk about JDK 8 (new year editio... Jaroslav Tulach
- Re: Lets talk about JDK 8 (new year ed... Michael Bien
- Re: Lets talk about JDK 8 (new yea... Neil C Smith
- Re: Lets talk about JDK 8 (ne... rangi.k...@siemens.com
- Re: Lets talk about JDK 8... Neil C Smith
- Re: Lets talk about JDK 8 (new yea... Jaroslav Tulach
- Re: Lets talk about JDK 8 (ne... Matthias Bläsing
- Re: Lets talk about JDK 8 (ne... Scott Palmer
- Re: Lets talk about JDK 8... James Gosling
- Re: Lets talk about JDK 8 (ne... Laszlo Kishalmi
- Re: Lets talk about JDK 8 (new year edition) Neil C Smith
- Re: Lets talk about JDK 8 (new year editio... Jaroslav Tulach
- Re: Lets talk about JDK 8 (new year ed... Matthias Bläsing
- Re: Lets talk about JDK 8 (new year ed... Neil C Smith
- Re: Lets talk about JDK 8 (new year ed... Laszlo Kishalmi
- Re: Lets talk about JDK 8 (new yea... James Gosling
- Re: Lets talk about JDK 8 (ne... Kirk Pepperdine
- Re: Lets talk about JDK 8 (new yea... Glenn Holmer