![]() The most advertised things I see in the Kotlin news the past years is Kotlin for the web (but no standard NPM compatibility), or Kotlin for Desktop with still many androidx imports. Kotlin could absolutely become a de facto standard in many companies imho, because the friction to move is low (compared to keeping up with Java versions for example, or moving to a new stack). Google is a very large Kotlin user and the second company with Jetbrains in the Kotlin foundation, but I see little "advocacy" from their side for anything Kotliny that isn't android.As much as I love IntelliJ, I see more and more folks using multiple IDEs but it's virtually impossible (today) with Kotlin Kotlin still behind the "IntelliJ walls".Kotlin improvements lately very much focused towards multiplatform, with (imho) little love given to the backenders comparatively.Java moving faster, making the "friction" of moving to Kotlin less interesting.:-)īeen asking that very question to so many folks at Kotlin conferences. Then I'll see how they handle such things. I'm moving on to Rust after I get my head around it more and become more productive. My goal is to get my career off of the JVM soon. In the end, do what you find works best for you. I would only want the help of configuring factories to instantiate the correct instance for the environment I'm in. I may look at something like Koin, or go back and look at Guice again (but I would like the "more safe" use of Kotlin if I can have it) as those seem pretty close to just being DI. The DI solution needs to be only a container and not an application framework with web servers, http clients, transaction managers, ORMs, and silly abstractions on top of other simple things. I'm not completely against DI if I find a need I suppose I'll go find one. People who want their DI (which isn't DI anymore, they are frameworks) will want their DI. ![]() I could talk about such things for a long time, but it's probably not worth it here. ![]() ![]() This simple example was posted here recently: I believe your are thinking too much about huge class hierarchies and complex object instantiation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |