4 ms·

Yes it was a nice/quick/dirty way to persist an object graph, I bet it's been abused richly in a lot of codebases out there, it'll be curious to see how this is

Yes it was a nice/quick/dirty way to persist an object graph, I bet it's been abused richly in a lot of codebases out there, it'll be curious to see how this is handled in terms of breakage i.e. the JDK that introduces this might be the Python 2/3 showdown (if that's still a thing). Be curious to do a Github wide grep for ObjectOutputStream or something similar and see what it's like in open source land.

sitkack 8y ago
Speaking of Python, pickle is `eval` soooo be a little careful with that one.
gmueckl 8y ago
This is made more exciting by the fact that Java rarely introduced big breaking changes in the past. Especially deprecated classes (java.util.Date...) never were actually removed. Starting this now is going to wreak havoc.
- Turbots 8y ago
  why is it going to wreak havoc? Java 8 will be supported until 2020 and Java 11 (next LTS version, due in September this year) will be supported until probably 2022. This change will come even after that. I wish they would have killed classes like java.util.Date long ago, since its one of the worst classes which is widely used in the JRE. Serialization was invented in 1997 and has no real usecase anymore.. You want loose coupling and tightly bounded contexts, not the other way around.
- djsumdog 8y ago
  We're already starting to see the effects in Java 9. Our team attempted to use it on our current project and many of our dependencies broke because they were using deprecated parts of the API that were removed. We ended up having to drop back to Java 8.