We are currently writing a multi-module server project in a mixture of Java and Kotlin. Java up to a particular date from which all new classes started being implemented in Kotlin. Only one little discomfort with proxies, everything else works smoothly. Then we have a related project that is being done entirely in Kotlin (except for a few entity classes generated by NetBeans in Java; this is only because I’m too lazy to write those by hand in Kotlin). The projects are over 20k lines so far and everything seems fine.

We’re using Java EE 7 (WildFly 10); JAX-RS (RestEasy) for REST. Kotlin plays nicely.

The issue with proxies is that CDI (Weld) requires bean classes and members to be non-final so that they are proxiable so you have to stick

open

on everything. There are active discussions (and on-going implementation) by JetBrains to alleviate this pain point. https://youtrack.jetbrains.com/issue/KT-12149 Also since Kotlin doesn’t have package-private access, things you normally make package private and annotate with

@VisibleForTesting

you now have to make public but Weld doesn’t like public fields. I’ve brought this up with the JetBrains folks on the #general channel and someone is looking into it. https://youtrack.jetbrains.com/issue/KT-525 https://github.com/hextremelabs/kotlin-weld-demo

We discussed performance issues in #ktor a little bit and since we touch Wasabi, Akka, Vert.x I suggested we migrate here. https://kotlinlang.slack.com/archives/ktor/p1478027503000514

I think we can make a community effort to setup kotlin-hello-world-web-server using many Java frameworks, starting with @rocketraman’s repo https://github.com/rocketraman/simple-http-benchmarks Anyone wants to contribute something, like Spring, SparkJava, etc?

I could contribute sparkjava

will you create a separate repo?

@kirillrakhman I can manage pull requests on my repo for now, if thats ok with @orangy -- we can move this to a jetbrains-managed repo later if necessary

Sure, I'm all for open community:)

my concern was the bad discoverability, because the repo is not kotlinm-specific and is about benchmarks, not hello worlds

or maybe your plan was to extend the repo first and then fork from it and convert it into a hello world repo?

@rocketraman is it okay if I change some gitignore stuff regarding the .idea directory?

Sure

I've found a config that seems to cause the least amount of pain between different machines

Also, I can rename the repo to reflect its hello-world nature as opposed to its benchmark-specific nature. That should be good for now.

Ok, I've found the current

.gitignore

config generally works quite well, but I'm happy to see improvements!

I'm also adding gradlew stuff to the repo

Good

so I'm writing the sparkjava benchmark in Kotlin?

sparkjava is not Kotlin specific per se

I'm dumb, I didn't realize the whole repo was in Kotlin

@rocketraman PR sent

@kirillrakhman Thanks, merged!

@orangy What is a good package root for a kotlin community project?

No idea, any suggestions?

org.kotlin.community

?

Works for me

I don't think it needs publishing anyway

To central or bintray I mean

Ah package, yes