The lack of an official JSON API has been a huge sore point for quite some time and has spawned dozens of libraries re-implementing the same thing over and over (GSON, Jackson, and even my own nanojson). I do hope that we avoid the DocumentBuilderFactory mistakes of XML and just end up with One True JSON implementation this time.
There is an official JSON API: https://jcp.org/en/jsr/detail?id=353 But it is unclear how many of the existing implementations conform to it, and it definitely doesn't work toward your misguided One True JSON Implementation goal.
Java 9 features announced
201–210 of 228 posts
Re: Java 9 features announced
#202My Wishlist: 1. Fix Daemonization! Publish an official blessed and supported way of daemonizing processes. Yeah sure, you can use Apache commons-daemon and others of it's ilk. And it will work. But it will feel hacked together (at least it does to me). 2. Fix Dependency hell! Publish a blessed / supported / standard of supporting / managing different classloaders. Java has this great mostly unused mechanism (classloa…
Re: Java 9 features announced
#203I thought one of the things promised in Java 9 was to finally fix the primitive mess, including all of the boxing and pointer chasing. Yet I can't find that here. I also thought that type reification was being researched. Does anyone know if either of these is still a thing?
Yes, they are both being worked on. They're just not sure they'll be ready in time for 9.
Re: Java 9 features announced
#204Earlier quoted context omitted.
Sorry to ask, but as a noob who just picked up Java, how do other languages address this issue? What's wrong with getters and setters?
To add another example to the list, Ruby lets you list which attributes can be read/written and which ones can only be read on top. Something like. class Car attr_reader :model, :company # only read attr_accessor :color # read and write end
This is pretty trivial so bear with me... If you have something that looks like this...
class Person
attr_reader :children
def initialize
@children = []
end
end
You can then do this... x = Person.new
x
You will have then altered the value of @children without completely reassigning it.Re: Java 9 features announced
#205I'm deeply missing hot swapping. I believed it could be included in java 9 but i think we have to wait...
Re: Java 9 features announced
#206Earlier quoted context omitted.
ah, understood. have you been tracking shenandoah? http://openjdk.java.net/jeps/189
I have heard of it but haven't read up. I think it's great that someone is stepping up to address the issue. Interesting that both the authors listed in the JEP work for Red Hat.
Re: Java 9 features announced
#207Earlier quoted context omitted.
What particularly is your issue around GC fragmentation? I ask because I had issues previously, but it was "solved" by moving to the G1 GC, I didn't know if you have considered the same.
G1 still fragments and does long compacting stop the world GCs. G1 pause times are still too long. G1 still doesn't have enough throughput. It's bad enough that people who care aren't using G1 yet. They still use CMS and small heaps and are careful to prevent promotion and fragmentation. You basically end up benefiting from GC for short lived allocations, but pay dearly for using Java when managing state the collecto…
Re: Java 9 features announced
#208Earlier quoted context omitted.
It seems that it is almost in prototyping stage, the usual suspects have already written a sketch of a future proposal: http://cr.openjdk.java.net/~jrose/values/values.html
Awesome! Thanks. I don't know much about the path from idea to standardized feature with the JVM. Is there hope for it in Java 9 or is this much farther out in the future? Probably first and more importantly, what is the chance for this even ever happening?
Re: Java 9 features announced
#209Does anyone know if project jigsaw will improve the startup time for JVM languages?
Re: Java 9 features announced
#210No language features?