If you look at the changes made in Kentico 8 API one-by-one, you will end up with a pretty long list. They are good for you!” Now, let me get down to the specifics of what I am talking about. So the message to you in my introduction above basically is, “Welcome the changes. We want to be the market leaders, and in order to do so, we first must become innovators. Simply put, we don’t want to stay frozen with what we have now, and become obsolete like dinosaurs (or some of the large well known corporates in the past). The whole exercise is simply about making things right and getting rid of the legacy obsolete (anti)patterns that no longer align with current trends. So, even if you don’t enjoy some of the changes that we have had to make right now, trust us, you will appreciate them in the future as they will also allow us to provide you with clear and efficient best practices on customization, development of new modules, and other stuff that you need in order to make your transition between versions smoother. Have a look at the following feedback example: Īs you can see, these changes truly are supported by a lot of opinions and votes made by you, our users and partners. Trust me when I say that we don’t enjoy refactoring very much or changing the API - in essence, this is all actually driven by your feedback and backed by a number of voices. Long story short: It takes some pain now to avoid larger pain in future. This process itself, however, comes with actual changes to the API because you can’t make anything better without changing it. As we announced a couple of times in the past already, we worked hard on improving the overall architecture and stabilizing the public API of the platform so that it doesn’t change as much in the future as it did in the past. It has been a long time since the release of Kentico 7, and exactly 18 months of development for Kentico 8. This article will give you more insight into the API changes made in Kentico 8, and also explain the reasons why these changes have been implemented. Improving API to be able to follow the latest trends and make it efficient is an important part of any platform life-cycle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |