Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Lew Newsgroups: comp.lang.java.programmer Subject: Re: no more primitive data types in Java (JDK 10+). What do you think? Date: Thu, 19 Apr 2012 17:31:27 -0700 (PDT) Organization: http://groups.google.com Lines: 64 Message-ID: <30566772.52.1334881887716.JavaMail.geo-discussion-forums@pbts20> References: <4f90a788$0$286$14726298@news.sunsite.dk> NNTP-Posting-Host: 69.28.149.29 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1334881964 877 127.0.0.1 (20 Apr 2012 00:32:44 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 20 Apr 2012 00:32:44 +0000 (UTC) In-Reply-To: <4f90a788$0$286$14726298@news.sunsite.dk> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.28.149.29; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T User-Agent: G2/1.0 X-Received-Bytes: 3577 Xref: csiph.com comp.lang.java.programmer:13667 Arne Vajh=F8j wrote: > Nasser M. Abbasi wrote: >> According to >> >> "To Java SE 8, and Beyond! Simon Ritter Technology Evangelist, Oracle" >> >> (Google the string "To Java SE 8 and Beyond!" and click on >> the PDF file, about the 5th link down the page) >> >> On page 42, it says: >> >> "Unified type system (JDK 10+) >> No more primitives, make everything objects" >> >> I've seen very little discussion on this very important >> subject. >> >> What do the experts here think of the idea? >> >> For me, and I am no expert, I think it will be good to have >> a consistent type model (everything is an object), but I am >> worried that the performance will take a hit (computational finite >> elements methods, large meshes, etc...), unless PC's and computers >> will become 1000 times faster by the time JDK 10+ comes in few years >> from now, which might be possible. >> >> Any one knows more information about this item? >> Any truth to it? Do you think it will really happen? >=20 > C# has it that way. No performance problem. It should > certainly be possible to implement. >=20 > (note: everything object does not imply everything > a reference type) And reference type doesn't inherently imply a performance hit. Java's Hotsp= ot famously enregisters and stack-allocates objects under the hood when it = deems it felicitous. > I don't know if it will actually happen. >=20 > And I don't think the practical impact will be big > if it does happen (neither performance nor the way Java code > is written). And it is quite likely that computers will be enough faster, if not 1000 ti= mes so, before Java 10 comes out. How much longer for even Java 8, and how = long was it between 6 and 7? Java usually has had about two years between v= ersions, meaning that Java 10 might be out in 2017. The very paradigm for c= omputing might render the notion of "primitives" irrelevant by then. Even a= ssuming current computing models, Moore's Law hints that we might see an ei= ghtfold increase in computer power by then. There is a movement in the Java community for value objects, as opposed to = references, in support of Arne's point.=20 There's also the point that source distinctions might look different in byt= ecode or machine code. What we might think of as an 'int' object at the sou= rce level might be treated as an ordinary machine integer at the lower leve= l. --=20 Lew