>But … KMP will fail to reach mass adoption because of human nature. People resist change and anything that is unfamiliar to them.
Yeah, it's not that. That is just a big hand waving argument, which one could say for anything, including stuff that will get mass adoption.
"Humans will never use C/C++/Python/Java/C#/JS/... because something something human nature. People resist change and anything that is unfamiliar to them."
The reason is KMP is just one offering among many others in the multiplatform "shared code/UI" space.
Kotlin is already niche anyway (despite being a good language), if the bar is about it "gaining mass adoption" in any grand way (comparable to Java for example).
If we mean mass adoption in a less grandiose way, Kotlin is doing alright, as do other new languages (Rust and Go for example).
>You lost 90% of them right there. They nearly all want to run for the hills. Java and the JVM have a great reputation in JVM circles (Java, Kotlin, Groovy, Scala, etc) but outside of that world people run as far away as they can from Java. It’s sad, but true. I’ve seen it multiple times in the last 20+ years of software development and I still see it to this day.
Yeah, not everybody is going to use Java. Not because "human nature", but because there are other options out there, people have investments in code/skills/time/libraries and so on, or prefer other languages.
One could just say the same argument about you not using Haskell for example, or C#, or whatever.
>We’ve been down the multiplatform road a number of times and it’s never become the panacea of development that proponents of each technological revolution claim it will be. All for the same reason I explained above … human nature.
Nope, the reason is all multiplatform offerings are crap, and have issues. Java never had a good native UI story. QT had its licensing baggage. C# was mostly a Windows thing, and Mono wasn't that encouraging. Electron is bloated. Flutter had a lot of bugs, and the language is changing a lot with each release. And so on.
>Not once has one of these platforms has taken the software world by storm. The one that has gotten the most traction is JavaScript, but it still has not taken over the world.
Like what, everybody using that and only that?
This is not "human nature" preventing it, but Javascript being good for particular things and not others, plus huge costs of migration where it could perhaps be a match (including rewriting existing code that works just fine with some other language, retraining costs in time and money, recreating libs that exist and do particular things in the other language's ecosystem, and so on).
>I’ve been saying for a long time now that we need to use the right tool for the right job.
Strange, for the most part TFA has been lamenting how not everybody rushed to adopt one single language or another, and how "bad human nature" prevents this.
Yeah, it's not that. That is just a big hand waving argument, which one could say for anything, including stuff that will get mass adoption.
"Humans will never use C/C++/Python/Java/C#/JS/... because something something human nature. People resist change and anything that is unfamiliar to them."
The reason is KMP is just one offering among many others in the multiplatform "shared code/UI" space.
Kotlin is already niche anyway (despite being a good language), if the bar is about it "gaining mass adoption" in any grand way (comparable to Java for example).
If we mean mass adoption in a less grandiose way, Kotlin is doing alright, as do other new languages (Rust and Go for example).
>You lost 90% of them right there. They nearly all want to run for the hills. Java and the JVM have a great reputation in JVM circles (Java, Kotlin, Groovy, Scala, etc) but outside of that world people run as far away as they can from Java. It’s sad, but true. I’ve seen it multiple times in the last 20+ years of software development and I still see it to this day.
Yeah, not everybody is going to use Java. Not because "human nature", but because there are other options out there, people have investments in code/skills/time/libraries and so on, or prefer other languages.
One could just say the same argument about you not using Haskell for example, or C#, or whatever.
>We’ve been down the multiplatform road a number of times and it’s never become the panacea of development that proponents of each technological revolution claim it will be. All for the same reason I explained above … human nature.
Nope, the reason is all multiplatform offerings are crap, and have issues. Java never had a good native UI story. QT had its licensing baggage. C# was mostly a Windows thing, and Mono wasn't that encouraging. Electron is bloated. Flutter had a lot of bugs, and the language is changing a lot with each release. And so on.
>Not once has one of these platforms has taken the software world by storm. The one that has gotten the most traction is JavaScript, but it still has not taken over the world.
Like what, everybody using that and only that?
This is not "human nature" preventing it, but Javascript being good for particular things and not others, plus huge costs of migration where it could perhaps be a match (including rewriting existing code that works just fine with some other language, retraining costs in time and money, recreating libs that exist and do particular things in the other language's ecosystem, and so on).
>I’ve been saying for a long time now that we need to use the right tool for the right job.
Strange, for the most part TFA has been lamenting how not everybody rushed to adopt one single language or another, and how "bad human nature" prevents this.