-
Notifications
You must be signed in to change notification settings - Fork 65
Make Collections Serializable #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Is that really required? Java serialization is not really that useful. It will also be dropped by Oracle at some point. |
Here is a clarification. According to Mark Reinhold (chief architect at Oracle): "[Serialization] was a horrible mistake in 1997," he said. "Some of us tried to fight it, but it went in, and there it is. ...We like to call serialization 'the gift that keeps on giving,' and the type of gift it keeps on giving is security vulnerabilities.... Probably a third of all Java vulnerabilities have involved serialization; it could be over half. It is an astonishingly fecund source of vulnerabilities, not to mention instabilities." Sure, this is a long term goal, but it is clear that Java Serialization was not a good idea in the first place. While it makes sense to support this for compatiliblty reasons, I do not think that it is worth adding to a brand-new implementation. Nowdays there are much better ways to achieve the same goal. |
Later we could make the immutable collections serializable by Kotlin Serialization. |
Closing this as I have no use case anymore for it. 😊 |
This would be useful to me to be able to pass PersistentLists inside java.io.Serializable classes between destinations in android navigation: https://developer.android.com/guide/navigation/navigation-pass-data#supported_argument_types |
The other collection types are serializable as well, there is imho no reason why the immutable versions should not be.
The text was updated successfully, but these errors were encountered: