So... here we go! ANNOUNCING KODEIN-DI 5.0.0!!! F...

# kodein

[salomonbrys]

So... here we go!
ANNOUNCING KODEIN-DI 5.0.0!!!

First of all, some acknowledgments:
- Huuuuge thank you to @olonho and his amazing team of Kotlin/Native. For creating the technology of course, but also for being ultra-reactive! Most of the bugs & crashes that I reported were fixed within 72 hours. Some missing pieces were prioritized to allow Kodein 5.0 to be compatible with Kotlin/Native. I have never worked with such a great team and it has been an honor to contribute, as little as I did, to this great endeavour!
- Great thanks to all of you who annimate this channel while I'm away. I've never been a social community guy, and it is because you answer here on Slack as well as on other medium that this community lives and this library finds it audience. So thank you to @Andreas Sinz, @streetsofboston, @jdorleans, @kailan, @dave08 and everyone that I forgot to mention here 😉
- Thanks to all of you who come with new ideas. 80% of Kodein-DI's features are because of your dissatisfaction in the current state of Kodein. Features such as subtype bindings, argument uptype handling, multiton, all matching retrieval, set binding, and much more are included because someone came and ask "How can I do that?"

Now, for the annoucements themselves.

First and foremost, Kodein-DI 5.0.0 stable is live in JCenter. It took some time because of a bug in JCenter (only half the packages were released).
There are two main differences from the previous beta 5 version:
- The packages have changed again (sorry about that): they are now inside org.kodein.di.*
- Introducing subtype bindings, which allow to register a parent type and the a binding factory that will provide a binding for each new subtype of this parent type.
As usual, everything is in the documentation (http://kodein.org/Kodein-DI/) and changelog (https://github.com/Kodein-Framework/Kodein-DI/blob/master/CHANGELOG.md).

Second, announcing the Kodein Framework (http://kodein.org). It does really not exist yet: Kodein-DI is (at the moment) the only released component of the framework. This framework will propose various components that are focused on multi-plateform development (JVM/Android/JS/Native/iOS).
Note that each component will be usable by its own and that Kodein-DI, as well as other components, will continue to also be focused on the JVM and Android. Being multi-platform does NOT mean sacrificing JVM only goodies. Kodein-DI 5 includes multiple features that are available only to JVM & Android, and those features will continue to be supported.
Some components of the framework (such as Kodein-JSON) will be focused exclusively on multi-platform and some other (such as Kodein-DI) won't. The choice is made based on the usefulness of the component outside of the multi-platform ecosystem.
The framework itself will aim to provide a full ecosystem to easily create business code, modules and architecture to be shared between platforms. In term, applications that are developed with the Kodein Framework should contain 60% to 80% of shared code between platforms.

Finally, to support all of that, I'm very happy to announce the Kodein company: http://kodein.net .
This company, based in France but active in all Europe, develops three major axes:
- Kotlin consultancy & development services.
- Kotlin training & migration programs.
- Kodein framework development & support.
If you would like to work or contract with us, feel free to contact me at [e-mail].
Note that the Kodein framework in general and the Kodein-DI library in particular will remain fully Open-Source and that the community will continue to be supported. I am Open-Source at heart and the company we are building is too. We plan to monetize through services: consultancy, SLA support, training, development, etc.
All of this is still in early stages.

In the meantime, I hope you enjoy Kodein-DI 5.0.0 😉
Salomon.

[arne.stockmans]

@salomonbrys Do you already know when we can expect other components to be available? Or is it still too early to talk about timings? 🙂

[salomonbrys]

@arne.stockmans This is, unfortunately, too early. At the moment, we are working on ramping up the company & acquiring our first clients. More will be announced as soon as possible 😉

[arne.stockmans]

Okay, too bad. Already looking forward to them!