hmm if the correct definition of an initializer is always this, we can automatically put to null the initializer after the first call ;)
I worked on a use case where I never put the initializer to null because I wanted to load some different remote data at each method call.
I think it's strange to have a no writable public property.