Everytime you think of Java you may think about types as of classes and primitive types. Not many, right? Well, there’s a major difference between the thing and handling it. The latter brings a lot of corner cases.

This is Serializing Java - a series about writing your own serializer in case you didn’t like other serializers.

Serializer can detect cyclic dependencies in two essential phases:

1. inspection of data structure
2. data serialization

Let’s dig into both of them.

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.

Every deserializer needs information about types - the data structure. In my serialization the deserializer can work behind network connection so it can’t count on Reflection mechanism. That’s why the serializer has to discover and serialize data structure that could be sent over the network and understood by deserializer.

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.

Why reinventing the wheel again? Why popular serializers are useless to my project - Entity Tracker?

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.

In previous week I had to resign from using Kotlin in one of my game projects. By porting the code manually I can point out what I didn’t like about Kotlin. Let’s see few differences between Kotlin and Java.

All your Java fields belong to us. Reflection is powerful but you have to remember a few rules before dealing with class fields.

This is Serializing Java - emerging series about writing your own serializer in case you didn’t like other serializers.

Let me introduce you Artemis Entity Tracker - a tool to be used for game development in conjuction with artemis-odb (which covers architecture called Entity Component Systems).

Forget about Object-Oriented Programming. Look at this flat world built of small data chunks and separated logic. A world easy to refactor. Meet Entity Component Systems.