Hacker News new | ask | show | jobs
by bitmapbrother 3535 days ago
I'd also add:

  Generic Specialization  
  Reified Generics  
  Native Function Calling
  Native Data Access
  New Data Layouts
1 comments

>Reified Generics

This will not happen.

Probably not at the language level. If you watch the Goetz talk you linked to he answers this at 50m36s. The bytecode and JVM will be able to represent riefied generics, but at the Java language level they'll still likely maintain erasure for Object types.

https://www.youtube.com/watch?v=Tc9vs_HFHVo&list=PLX8CzqL3Ar...

I know, but with the JVM having full support, that might eventually change in Java 11 lets say, after the experience how everything went.

Brian did not state they will never do it.

Also the other languages could take advantage of it anyway, even a reiffied version of Java for example.

Reified generics for reference types is a really, really bad idea. It solves a minor, itsy-bitsy-tiny problem, but pretty much ruins sharing of data structure among languages, because it bakes a specific variance model into the classes. For value types that's not a problem because they don't support subclassing anyway.
> For value types that's not a problem because they don't support subclassing anyway.

Could you please provide a reference for this? Even a broad one like "a post on the Valhalla mailing list during the past summer" would be very welcome.

I'm eagerly awaiting for this feature and not being able to extend user-defined value types would be a bummer.

Good thing Kotlin already supports reified generics (with the current caveat that they must be used in inline functions), Java the language is less important these days than the JVM having support for the feature.
Java the language is still very important, it is the systems programming language of the JVM.

On my .NET projects we get a full installation from Visual Studio on the development machines. Which means C#, F#, C++ and VB.NET available.

On my Java projects those machines have usually Eclipse + JDK. JARs are either vendored or make use of an internal Maven server.

I am yet to be allowed to use anything other than Java (the language) on those kind of projects.

Most customers want replaceable consultants so they don't allow us to go outside of their standard stack.

The joys of working for a company with in house developers, as long as I don't use something that would be extremely difficult to bring a new developer up to speed on (accounting for the necessity of said solution as well) I can generally make a case to use whatever.

I've got a mix of C#, Python, Kotlin and pl/pgsql code running in production right now and we've also for projects written in Node.js that are live as well. I've even got some F#!

Those are not fully reified generics, only the native types generics are reified.
>This will not happen.

This will happen.