@KoLoyYee Maybe one day - when I find the time 😊

@marcioendo I will talk more about all this at some point, yes 😊

One of the reasons Java Serialization has "died out" is that it assumes that both the serializing and deserializing code is Java code. Quite often, that is not the case. Often you want to serialize some objects in Java and deserialize them in JavaScript (backend objects sent to frontend). Or - you may serialize some objects in a service, and have the remote client decide what language (C#, Go, Rust etc.) they will be deserialzing the objects in. Or - the client is Java and you don't know what the service is implemented in. The new Java Serialization standard changes this somewhat - allowing you to choose the serialization encoding yourself. But it comes at the cost of not being able to serialize cyclic object graphs... However, we already have lots of APIs in Java that can do precisely this. Do we need one "hardcoded" into Java ?!? #Java

Interesting !! 😊

@KoLoyYee @java Thank you ! 😊

When being serious about Compositional Software Design (designing your code base for composability) - you will often experience these two phenomena impact your code base size: 1) Decompositional Expansion 2) Compositional Contraction First, your code base will expand because you are breaking your code base into many smaller pieces that can be composed together to form solutions. This phenomenon (phase) is what I call the "Decompositional Expansion". Later, your code base will feel like it contracts, meaning it does not grow as fast in size anymore as it did in the beginning. It feels like you can add new functionality with little code (and little effort). This phenomenon (phase) is what I call the "Compositional Contraction". During this phase you are starting to reap the benefits of all those reusable components you created during the Decompositional Expansion. Have you experienced these two phenomena in your code base size growth? ☺️ I am covering these phenomena in my upcoming video about Compositional Software Design ☺️ Seems like it will be one of my longest videos to date! 🫢 #CompositionalSoftwareDesign #CompositionalDesign #SoftwareDesign

@ThePrimeagen AI can be useful at answering questions you might otherwise have to search a lot for answers to using search engines.

@robertbrautigam While that might sound true from an OO theoretical perspective, in practice that is not how we send data between applications today. We do actually (most of the time) just send "bags of data" between computers.

@ivantopo That would also be my preference. I see no real need for Serialization built into the Java language - the way the world looks today. We can do that just fine with the libraries that are available today, I feel.

RT @KoLoyYee: If you want to learn Java Concurrency or concurrency, this is the most friendly, easy-to-understand playlist by @jjenkov