Not yet, but it’s coming

Network stack on all platforms requires a lot of work on all platforms. Buffers, sockets, channels, coroutines, etc. Another approach that we are testing is to use platform’s native http client (such as on iOS), and then have some common API on top of it. But that also requires a lot of design work, and not all platforms have native http clients. Basically, it’s a complex project 🙂

i can see the complexity

I know it’s usually used on Android but why not retrofit?

you can use okhttp of course, if you’re in a JVM world

The only problem is the reflection

Another solution would be to make a gradle plugin that uses the kotlin parser to parse an AST from common code and use that to allow to generate new code before actually compiling everything but I unfortunately don't have the time to work on such plugin

Is there a list of companies using Kotlin for backend development somewhere?

I guess not the entire list, but a handful of large companies using it in production. Most of the reference companies i’ve seen are only for android

@Jonathan Walsh We (Hexad GmbH) use Kotlin + Spring Reative for backend development in Automotive Industry

the bank n26 uses it

we use it in some teams here at OLX

We use it for backend development at Samsung

We use it at Moip (Brazilian payment gateway company)

We use it at Netflix.

0

We use it at Luxoft for production with Spring Boot and quick prototyping

Over at Vayana we used it to fully write a GSP (It is an acronym for GST Suvidha Provider which is an API based service that connects up corporates, ERPs, accounting systems etc to India's GST Network through which all the invoices in the country get reported to the Indirect taxes authority and reconciled). https://vayana.com/gst/gsp/ (Trying to not make this a plug, but its hard to explain to an international audience)

Every project I wrote since kotlin release was on it and spring.

In Spring Boot, the

@Autowired

annotation is intended for dependency injection. I've seen examples use it either as a constructor for classes or just as class variables - does Kotlin have a certain attitude of using

@Autowired

compared to other Kotlin dependency injections that can be found like Kodein or Injekt?

My preference is always to use @Autowired on constructors but that applies to any code I might write in Java as well. I have a visceral distaste for field injection and like things immutable so don’t use setters.

I think Spring Boot supports JSR standard DI annotations as well

sorry, I think I’m misreading your question

Most Spring developers will find use of

@Autowired

significantly less surprising than alternatives so unless you have a strong reason to do something else, I would go with

@Autowired

I think that helps my understanding a little bit - seeing the 2 usage examples did confuse me a little. I'm attempting spring-social-[media] for authentication to pull data - I was previously using hard data surround the object 'Card' in addition to a parser for a

markdownConverter

for rendering mustache files: now that I'm ready for real data, my app broke, complaining about my constructors for my controller. I don't like it, but I am going to try moving the`markdownConverter` as an

@Autowired

field

a good portion of this issue is related to my limited understanding for Spring Boot, but my html parser should not be necessary as a constructor for the controller class if it's essentially a service I'm using

What’s the error you get? There’s a kotlin-spring lib that will automatically enable @Autowired on the constructor of any @Component (or whatever other relevant annotation) type.

@Autowired

was one solution I thought of (not sure if it will work), but Kotlin does have a lot of great dependency injections that could be interweaved into other classes

Before, I had something like