Kotlin Census 2017


Hello!

Every year we run the Kotlin Census survey so we can get the latest feedback from you, and how you are using Kotlin in your projects. If you still don’t use Kotlin, we would like to understand your reasons why and your opinion of the language is exceptionally important for us as well. If you filled out the survey last year, thank you, it would be really helpful if you could please do it again: we’re interested in the up-to-date information, we’ve also added a few new questions and response options based on last year’s results.

As such, we’re asking you if you could kindly give us two minutes of your time and fill out the following survey.

Please note that by providing us with your details, you are not automatically giving us consent to use your name, application or company name. We would always ask for written confirmation from you before doing so.

Thank you!

This entry was posted in community. Bookmark the permalink.

25 Responses to Kotlin Census 2017

  1. BabeDev says:

    Kotlin is great

  2. have you mistake katz library with kategory.io?

  3. A certification on Kotlin from jetbrains would be great.

    • Andy Marchewka says:

      Love that idea! With a functional programming component, coroutines, and specializations for Android, JavaScript, HTML, etc.

    • Louis CAD says:

      Your open source code on GitHub can be your certification 😉

    • mdevs says:

      That would produce a legion of “certificated” developers who don’t know sh** about programming; Just like what happens in Java. Maybe it would be a good idea if passing it is extremely difficult, and with extremely difficult I mean <15% of applicants would finish the process.

      • Alexander says:

        You are not quite right. From our experience (a big IT company), the guys who pass Sun Certified Java Programmer exam with score > 80% (we require it internally) are quite knowledgeable in Java and do not make false assumptions about language and API. This does not prove they can develop things, of course, but you shouldn’t consider only exam certificate when hiring devs, should you ?

      • Antekm says:

        I remember that learning for Java certification years ago was a good occasion for me to explore and learn some more obscure aspects of the language (and in general some things that I didn’t know so well)

        With Kotlin being rather new (at least in terms of adoption) having certifications could make up for lack of experience in this specific language (that can be a factor for people who might decide not to go for Kotlin as there’s no one with good experience in it in the company)

  4. Roman Doboni says:

    Can you pls put the submit button near the “accept terms …” checkbox? Took me a while to find it on mobile.

  5. Mike says:

    For those who may be filling this out on mobile (at least on Android Chrome), the “Submit” button is fixed to the very bottom right corner of the page.

    • Nils Breunese says:

      Thanks for that, I don’t think I would have found it (on my iPhone SE) without this comment.

  6. Jonathan D'Orleans says:

    I work heavyly with ML and AI and would love to have Kotlin as a primary language in the field instead of Python. I’m also working on openning a few libs to help this movement. Thx for the great work!

  7. williamwallace says:

    kotlin is simple, beautiful, efficient Android language

  8. Arslan Charyyev says:

    Please allocate more human resources to android support. For instance anko is fascinating and promising library, but lack of documentation and a single maintenainer makes it impossible to use it in production reliably. Thank you.

  9. John says:

    What I’d love to see from you guys, are some production quality examples on github with proper project structure and “kotlin-way” of writing code, so people can follow some guidelines and produce good code.
    As with all available code snippets and “hello world” examples in “main” method is not enough to teach people to write good quality code.

  10. Honestly after being on Swift and Kotlin straight for the past 2 years, it’s clear Kotlin is much further behind Swift at a holistic, production-quality level.

    For example, the lack of language-level array/dictionary subscripts and having to use library-level functions for simple nullable logic (ie: instead of Swift’s powerful “if let ….” / “case let …” ), let alone the whole mess around Delegates.observable and the various limitations of mixing them with ‘lateinit’, lazy etc. makes Kotlin feel very half-baked and immature still. There is still no proper way to check whether something has been late-init-ed yet (ie: Swift’s ‘trust-me’ operator ) and thus several scenarios around lazy-loaded data have to be mis-modelled as optionals instead of conditional late-inits. These kinds of things showcase that there were a lot of great POCs in the language in the exploration of introducing nullables/read-only to the JVM – but those things were never re-examined and re-designed ground up in the language. And that’s a damn shame.

    The fact that resources are being poured into going cross-platform (JS, Native) is a clear mis-prioritization as it’s going to spread the half-baked state of the language further and make it orders of magnitudes harder to make these much-needed changes – ie: or worse yet never happen. We saw this happen with Java VS C#, where Java got stuck a decade behind based on the premature opening and spreading of unproven approaches. It is happening right now for Kotlin VS Swift and I don’t want to see you guys fall in the same trap.

    As it stands, compared to any other JVM language Kotlin takes the crown, and you guys have achieved incredible things to take Java and Android forward into the modern age. But ’tis not yet the time to bring it outward to other platforms, this is the time to fix everything from all the lessons learned and from the inspiration you’ve gained from Swift – and make Kotlin a truly great language that’s WORTH bringing to other platforms.

    I hope you guys seriously reconsider this prioritization and focus again on making Kotlin better/cleaner/meaner. The alternative is that Swift WILL go cross-platform at some point (Silver is already on it – http://elementscompiler.com/elements/silver/), and once that happens Kotlin will be behind in a way that you will never be able to catch up / compete.

    • Evan Nelson says:

      “For example, the lack of language-level array/dictionary subscripts and having to use library-level functions for simple nullable logic (ie: instead of Swift’s powerful “if let ….” / “case let …” )”

      I disagree. I think that JetBrains’ decision to make these things library-level instead of language-level is the right choice. Why does the language itself need to have built-in support for things that can just as easily be implemented as library functions? That makes the language heavier and thus harder to maintain. To be honest I’m disappointed that they’re adding array literals, but that one was just too popular in the last survey.

      • Ole Sandum says:

        I wholeheartedly agree. When I first saw they’re going to be adding array literals I was confused as to why. I still don’t get it.

      • Perhaps the same reason such as any language feature is useful. For brevity, adoption and moving our industry forward.

        The same could be set about C# Task library. Why bother adding ‘async’/’await’ keywords? Because they were able to achieve an order-of-magnitude improvement in simplicity and adoption when they did. The way the go there was indeed to introduce it as a library-only feature for an entire generation of the language – and to stabilize it and bring it into the language once they were confident in the implementation/syntax.

        We should not settle for anything less with Kotlin. It’s okay to start at libraries to get the POCs out and collect feedback from the community – but especially with Swift leading the way and showing us mature, proven ways that it can be done, Kotlin should aim to minimize time spent in incubation for features and evolve the language / simply syntax – and stay closer to par with the growing alternative (Swift).

    • Gerald says:

      Agreed. Jetbrains should concentrate their resources on polishing Kotlin.

  11. Gert Claeskens says:

    Or ‘Kotlin Kings’ in analogy with Java Champions :)

  12. Eric W Clarke says:

    Looking forward to learning more

Comments are closed.