-
#TouchlabShare chatting about Kotlin 1.4 updates starting now 🎉 @TouchlabHQ/1299389301042475008Permalink
♻️ 1 Retweets ❤️ 1 Favorite Mood +3 🙂
-
Permalink
-
We have pushed out all our library updates for 1.4. Very excited because this is the first major release since the kotlin native era #TouchlabSharePermalink
-
Kotlin Native is not binary compatible right now. One thing interesting this round is that we got a long preview period so there's been time to do tests, make sure things are working. By the time the major release came out, we were in a really good place #TouchlabSharePermalink
-
We started implementing CI for our libraries. @kpgalligan thought he wouldn't be building Windows binaries again but he's surprised himself. #TouchlabShare
-
Back in 2010 @kpgalligan did a port of ORMLite and it was huge because #Android was new. #KotlinMultiplatform puts you as a mobile (#iOS or #Android) in a similar position. We helped bring SQLDelight to multiplatform and it was huge. #TouchlabSharePermalink
-
github.com/russhwolf/multiplatform-settings was one of the first multiplatform libraries @RussHWolf was inspired by a conference talk @kpgalligan gave about the budding ecosystem of #KotlinMultiplatform #TouchlabSharePermalink
-
We're seeing a lot of people build logging libraries now. It makes a lot of sense to get started there. We have our own github.com/touchlab/Kermit which was a fun naming process #TouchlabSharePermalink
-
The Kotlin 1.4 release is really interesting because it included compiler and compiler plugin updates that support a lot of important stuff, for JetPack Compose not needing a special kotlin compiler #TouchlabShare @AndroidDev/1298668020219424772Permalink
-
A lot of people were waiting on the alpha, and one technical reason it was in preview mode was because Google needed a fork of the official Kotlin repo, now they don't need a fork. #TouchlabSharePermalink
-
The change allows for more robust support of multiplatform libraries, tooling, and applications, too. The architecture for JetPack Compose is not specific to Android, and there is work bringing it to Desktop. It is feasible to bring it to iOS #TouchlabSharePermalink
-
The last 5 years of @kpgalligan's life have been making #Android code work on #iOS but focused on the logic, not the UI. #TouchlabSharePermalink
-
Q: What is the state of coroutines? A: Next week we'll be going more in depth on that. Another question is "when?". We don't know but what we do know is it will not be a couple months, more like next year. #TouchlabSharePermalink
-
The single-threaded branch: You can do coroutines on one thread to do asynchronous programming, but you can't cross threads. The multithreaded branch: This branch will stick around until the memory model changes. 👏You can use it in production👏 #TouchlabSharePermalink
-
Ktor is now using the mt-coroutines branch which is a statement of trust in how ready it is. There are things to keep in mind about Ktor with mt-coroutines. If you have a giant json file, it will be parsed in main thread, but calls are executed in background #TouchlabSharePermalink
-
Q: Multiple shared modules in an iOS app in 1.4? A: will still have an open ticket to check if you can have two static frameworks. We will update the blog post regarding this soon touchlab.co/multiple-kotlin-frameworks-in-application #TouchlabSharePermalink
-
We also have a blog post coming out soon talking about framework sizing which is really important if you are including multiple frameworks in your iOS app #TouchlabSharePermalink
-
Q: How good is KMM? A: This is not a binary question. It's related to whether it is production ready. There are many people putting it into production. The question is more are you willing to deal with the current limits? [JM: @piannaf/1206691901015044096] #TouchlabSharePermalink
-
Q: How to get started? A: KaMP Kit github.com/touchlab/KaMPKit Kotlin Slack (we are always there): kotlinlang.org/community/ Hire @TouchlabHQPermalink