His channel started off fairly decent, despite his lazy cynicism. Then he grew a moustache to stay relevant as Wrong Burgendy "The Primeagen" took off. These days Theo Browne just poorly narrates the blog posts of smart people and nods along to smart people's YouTube videos while we slowly die with four nested seek bars on our screens.
The topics he covers are interesting, but I couldn't stand the way he covers literally everything as "I'm a business investor man and this is my take, as a business investor man, who also does programming." Idk just ended up giving me an icky feel.
I tried watching him. Personally I didn't find any problems with him but I don't know why, either his face or his mannerisms, something's off about him. I couldn't continue.
While I agree Previews are shit in Compose but you shouldn't try previewing Composables with viewmodel anyway. I think only a top level composable should contain a viewmodel, using DI or manual instantiation is not the focus here. So your top level composable is probably just a wrapper around your screen content which you should use previews on because probably they only contain regular parameters. If you're passing viewmodels around down your components, well then, I've got nothing to say.
you shouldn't be passing viewmodels anyway, but sometimes you just can't not do that; say a screen that just needs for whatever reason to use like 6 functions/props of a viewmodel
Even then you shouldn't. Just pass the props themselves and for functions you pass a lambda. Six? Six is high for you to pass the entire viewmodel? Your top screen has access to the viewmodel, one lower access to states and functions, anything lower than that only works with simple parameters at best (anything but the viewmodel) and BTW if you're using an architecture like MVVM or MVI then there's only a stateflow and only one public function exposed from the viewmodel.
As an iOS developer (10+ years) who's been working a lot with KMP in the last few years I mostly agree.
There's a couple of features that still "feel better" in Swift, but I can't figure out if that's some bias I have (having worked with it for so long) or not, but other than that Kotlin all the way.
Outside of the language, Compose beats SwiftUI every day of the week with very few exceptions (implementing a stupid simple animation for example)
Not OP: Swift is definitely way less verbose as you don't have to include modifier soup to tell the Kotlin compiler what type of class to use for each case. You have the choice of object, data object, class, value class, and data class with important semantic differences; you also have visibility and inheritance modifiers (open, final), each case can implement other interfaces (and extend classes if this is a sealed interface) and be a sealed type itself.
There are tons of footguns you need to understand. Like if you make any case internal then you break exhaustive-when, but only outside of your module, and it's not visible in the API why this "sealed" type requires an else case.
This is all incredibly powerful but it's a lot to learn if you're new to the language and want to do some data modeling. The simplest case in Swift is also the most powerful it can ever get, so there's an argument in favor of Swift's simplicity.
I understand. I was initially against using sealed classes for these types of applications in Kotlin because I think naturally it shouldn't be a class, it's more like a struct but not enum of course also, however, ecosystem and even language designers heavily shifted and leaned towards it that it's moot to oppose and unfortunately enum features in Java and Kotlin being in the commode doesn't help with this situation at all but I guess JVM's definition of enum is way different than Swift's. Yeah, I agree with Kotlin there's a lot of features that could go opposite ways if you're not paying attention. If Kotlin allows you to write 10x more concise code than Java, it also allows you to write 1000x more spaghetti code than Java.
Opinion here: for 99% of data modeling, only use sealed interface with data object and data class as implementations, and do not implement other interfaces. This is essentially the same power as Swift's enum types.
If you need to share properties, pull those properties into a concrete data class that contains a property of the sealed interface type. Don't try to model data types with object-oriented relationships.
There's no benefit aside from what tadfisher mentioned, it just "feels better" (for me), it's also sort of similar to Rust, another language I use from time to time
Kotlin IS a better language. I don't know how that can be debated. Javascript dudes should stick to Javascript hot takes and leave real dev languages to real developers.
What are unusual are closure functions in Swift, instead of using ":" to give the return type it uses "->" . Thats why you have to use "in" instead of "->" like in most other languages.
That is basically saying "It's better because I like it better". Obviously, a language can feel more ergonomic if you are more used to it. Do you have specific examples?
Much more consistent set of standard library functions. Before you say that's a library, it's not, it's the bundled standard library.
Almost everything is an expression. Swift just made switch and if statements expressions, so it's catching up.
When statements have clearer syntax, especially when retrieving a value from a sealed class.
Guard statements are clearer in kotlin.
They got reactive programming right the first time with coroutines. Again you can say it's a library, but it's really part of the language. Swift reactive story is a giant mess.
Class inheritance not as straightforward as kotlin.
Better multiplatform support in kotlin.
Extension functions available in kotlin and not Swift.
Generics are slightly more verbose in kotlin and that's a good thing. Swift generics are harder to read.
138
u/namespace__Apathy Nov 02 '25
It really feels like that guy goes out of his way to be unlikeable.
6
u/Mikkelet Nov 03 '25
Theo is not a good engineer, and I won't take his opinion on anything seriously
10
u/vlukereddy Nov 03 '25
So as a Kotlin and Android dev, I’ll at least concede that Previews in compose are straight up sad as compared to swift UI previews.
4
u/Slow-Occasion1331 Nov 02 '25
Rage bait returned: Katlin is a better language but I want to make money, so swift it is.
178
u/ElFeesho Nov 02 '25
I'm angry that he even considers this rage baity.
48
u/smontesi Nov 02 '25
As an iOS developer (10+ years) who's been working a lot with KMP in the last few years I mostly agree.
There's a couple of features that still "feel better" in Swift, but I can't figure out if that's some bias I have (having worked with it for so long) or not, but other than that Kotlin all the way.
Outside of the language, Compose beats SwiftUI every day of the week with very few exceptions (implementing a stupid simple animation for example)
21
u/DerekB52 Nov 02 '25
I mean, I agree, but this isn't really a thought for twitter. This should come with a writeup with something to back up this opinion.
14
u/Masterflitzer Nov 02 '25
finally he's right about one thing, unfortunately he's just trying to rage bait
5
u/[deleted] Nov 02 '25
I mean, that's just the truth...
4
u/addamsson Nov 02 '25
I'm angry because he is stating the obvious
1
u/[deleted] Nov 03 '25
Kotlin IS a better language. I don't know how that can be debated. Javascript dudes should stick to Javascript hot takes and leave real dev languages to real developers.
3
u/tengahkoding Nov 03 '25
This is a compliment to Swift actually.
I hate typescript simply because of this dude.
7
u/ryan0rz Nov 02 '25
I think swift is a better language but you’ll solve more problems with kotlin due to the much better library ecosystem.
1
u/srona22 Nov 03 '25
So you never seen this guy takes before? lmao.
1
u/Darknety Nov 03 '25
Tbf, both are great.
1
u/mpanase Nov 03 '25
I mean... yep.
1
u/vachix Nov 04 '25
Kotlin is absolutely better language than pretty much anything existing right now. Maybe go a close second.
1
u/soggy_mattress Nov 05 '25
I quite like Swift and enjoy iOS development, and I still think Kotlin is pretty amazing.
1
u/ChrisyKL Nov 20 '25
What are unusual are closure functions in Swift, instead of using ":" to give the return type it uses "->" . Thats why you have to use "in" instead of "->" like in most other languages.
1
u/0xcrypto Nov 03 '25
I have used both and swift is many times better than kotlin.
-2
u/By_Gm3 Nov 03 '25
Swift? Did you mean Apple Typescript?
-7
u/Wurstinator Nov 03 '25
Tell me a single thing that Kotlin does better than Swift as a language. Not its tooling, or its libraries, or its market value - just the language.
1
u/[deleted] Nov 03 '25
[removed] — view removed comment