Ktor

As a tooling company, we do realise the importance of providing proper support for the languages and frameworks you use. In the case of Ktor, we started this journey by rewriting support for IntelliJ IDEA Ultimate completely from scratch, and the first step was a new and simplified project wizard, which has already been announced. With the 1.5.3 update, we're improving the options in the wizard, as well as bringing new functionality! New Project Enhancements The Project Wizard comes with two new options: Storing configuration Via the Configuration in dropdown, you can define whether you want

We're very excited to announce the Ktor Early Access Program, where you can get access (thus the name) to things we're working on that won't be available in the currently released version. Often times we'd like to introduce new functionality or APIs that may not be backwards compatible, and get these out to you as soon as they're ready for feedback. That's what our EAP program is about. It's important to understand that while these are not marked as releases, they do go through the same (if not more) tests and checks that our releases go through. We do encourage folks to try EAPs builds, but

We're happy to announce the release of Ktor 1.5.0, which comes with new features, bug fixes, and new docs! Features 1.5.0 is the third and final release for this year, inline with our promise to have three major or minor releases a year, and a minimum of one patch release a month. We're happy to say that so far we've managed to more or less keep this promise, albeit with an ocassional delay at times. In this minor update we have a series of new features including: New Development Mode Ktor provides a series of features targeted at development, such as for instance auto-reload as well as extend

Design in the open Ktor was created as an Open Source project and continues to remain one. During its development, feedback from the community has and continues to be fundamental, and very much appreciated. We'd like to take this to the next step by having all our design decisions in the open. The process will work as follows: Step 1 We create a ticket on YouTrack of type Design, and in it we'll lay out: Description of the issue What it is that we're addressing. Is it a new API? Is it improvements on existing APIs? Is it internal architecture? Current State If applicable, we outline the curren

For those that aren’t aware of the origins of Ktor, it was started by Ilya Ryzhenkov at JetBrains several years ago mainly inspired by Wasabi and Kara. Since then, it has evolved and is used internally at JetBrains on a number of products, including our newest one Space. Of course, Ktor is also being used quite extensively outside of JetBrains, and every day we learn about more companies and products that are built on top of it. It has become a core component of the JetBrains family of products, and moving forward we will be investing much more into Ktor. The year ahead As a first step, and i

Welcome First off, we’d like to invite you all to the new Ktor blog, where we’ll be sharing a variety of information, including plans, features, releases, etc. More importantly we hope for this blog to become a bi-directional communication channel, where we also receive your feedback!  Moving to YouTrack Now onto the topic of this post, which is migrating to YouTrack. At JetBrains we have many things planned with Ktor and we’ll be sharing this with you all in the coming weeks, but as a first step, we want to improve the support and attention we give to bugs and feature requests.  Up to now we’