Please don't stop making videos! I JUST discovered your channel and sat through 2 hours of content already. Keep up the good work! I'm fixin' to watch another episode. lol
I was very disappointed with Kotlin Native when they said they were dropping support for ARM32 and MIPS32 (and that's most of my dev. boards out of the window)... so it's more like "run everywhere, as long as your hardware is 64 bit". But, having come here from your Zig episode, I'm bound to have my grumpy hat on towards other languages. ;) Loving your interview skills... hope this series keeps going for a good long time. EMACS Vs vi... pah! nano is the way to go! ;)
I think jetpack compose is an enigma wrapped in a mystery. So far I think Kotlin is fine. But if could build an android app in vanilla javascript, html and css, it would be significantly more intuitive than kotlin compose. It is nothing like react. But a wrapper than made it act like react and mui might be nice. But fun?!? No I can't say it is a fun language. But that could just be a skill issue. I prefer the older way of styling with xml.
I'm very interested in this interview, since I have to use Kotlin in my day job, and it feels like a very poor language with some very strong opinions not rooted in fundamentals. I hope to find out how they got there, and whether its rationalization is as confidence-oriented as I am unfortunately expecting - hope to be proved wrong. I preemptively thank you for having the interview regardless.
cannot get over the oop leftovers in kotlin. it just comes form java, unfortunately. they cannibalized some fp, but it's still all bases in classes and the marriage of behavior and data. same with scala, by the way. as long you're married to the jvm, i cannot see how you can get away from oop. maybe it's personal, but I see that as something to get far, far away from. it's gotten way overblown.
@@eskii2 tailrec keyword exists in Kotlin for a reason, so it absolutely supports tail recursion. Since Kotlin supports higher order functions, currying can be achieved (through Arrow for example). Not sure what's wrong with the type system. If it's about ADTs, you can achieve what you want through sealed classes and pattern matching. Kotlin is not Haskell, but it doesn't need to be.
Please don't stop making videos! I JUST discovered your channel and sat through 2 hours of content already. Keep up the good work! I'm fixin' to watch another episode. lol
Thanks - I'm glad you're enjoying them!
We have about 10 future episodes already recorded, so I can 100% guarantee the next few months. 😄
I was very disappointed with Kotlin Native when they said they were dropping support for ARM32 and MIPS32 (and that's most of my dev. boards out of the window)... so it's more like "run everywhere, as long as your hardware is 64 bit". But, having come here from your Zig episode, I'm bound to have my grumpy hat on towards other languages. ;)
Loving your interview skills... hope this series keeps going for a good long time.
EMACS Vs vi... pah! nano is the way to go! ;)
nice show!
Your voice is very calming.
Thanks you. 😊
I think jetpack compose is an enigma wrapped in a mystery. So far I think Kotlin is fine. But if could build an android app in vanilla javascript, html and css, it would be significantly more intuitive than kotlin compose. It is nothing like react. But a wrapper than made it act like react and mui might be nice.
But fun?!? No I can't say it is a fun language. But that could just be a skill issue. I prefer the older way of styling with xml.
I'm very interested in this interview, since I have to use Kotlin in my day job, and it feels like a very poor language with some very strong opinions not rooted in fundamentals. I hope to find out how they got there, and whether its rationalization is as confidence-oriented as I am unfortunately expecting - hope to be proved wrong. I preemptively thank you for having the interview regardless.
will kotlin support VR? or oculus VR?
I can't use a language where I have to type 'fun' to create a function.
cannot get over the oop leftovers in kotlin. it just comes form java, unfortunately. they cannibalized some fp, but it's still all bases in classes and the marriage of behavior and data. same with scala, by the way. as long you're married to the jvm, i cannot see how you can get away from oop. maybe it's personal, but I see that as something to get far, far away from. it's gotten way overblown.
It's probably more down to its Java interop than the JVM, or is there something about the bytecode that makes oopiness necessary?
Kotlin is just java in other clothes. No sure I get the appeal. Having all the problems of java.
What problems of java does Kotlin have?
@@munchymanjaro9070 Same type-system. Also Lack of currying. Equals / hashcode / toString implemented on all objects. Lack of tail recursion. Etc
@@eskii2 tailrec keyword exists in Kotlin for a reason, so it absolutely supports tail recursion. Since Kotlin supports higher order functions, currying can be achieved (through Arrow for example). Not sure what's wrong with the type system. If it's about ADTs, you can achieve what you want through sealed classes and pattern matching. Kotlin is not Haskell, but it doesn't need to be.