Rust Programming

8159 readers

1 users here now

founded 5 years ago

MODERATORS

nutomic@lemmy.ml

Joe@lemmy.ml

AgreeableLandscape@lemmy.ml

Do you think Rust should architecturally replace Kotlin? (lemmy.ml)

submitted 3 years ago by AgreeableLandscape@lemmy.ml to c/rust@lemmy.ml

5 comments fedilink hide all child comments

Apologies if this question isn't really appropriate for this community, but Rust and Kotlin are my two favorite programming languages, and currently, I use both for different projects. However, I'm curious as to if people here think Kotlin still has a place when Rust exists? I'm specifically speaking architecturally: disregarding existing legacy code or support, do you think in the future, the Rust platform should replace the Kotlin platforms (JVM, LLVM Native, Android, Web) for everything Kotlin can do, or do you think Kotlin can do some things better than Rust?

top 5 comments

sorted by: hot top controversial new old

[–] dessalines@lemmy.ml 15 points 3 years ago (2 children)

I'm more experienced with java, but have used kotlin a bit too. The JVM languages are extremely versatile and capable of doing anything, but kotlin is probably the best of them in terms of syntax.

That said, after dealing with java's garbage collector, I don't think garbage-collected languages have a place in the future. Rust showed me that despite claims of garbage collected languages being easier, simple scoping and borrowing don't really add any complication, and are better in terms of memory in the long run, and a better choice for pretty much every type of application.

But practically of course browsers aren't going anywhere (so we'll still need to learn javascript / typescript), and neither is android (so we'll still need to learn a jvm language). I'll still use kotlin, but only for android. Rust already has functioning web servers, UI toolkits, CLI toolkits, and everything you need for desktop or server apps.

[–] qaz@lemmy.world 11 points 1 year ago* (last edited 1 year ago) (2 children)

Circular references and objects shared by multiple scopes (e.g. a lambda that uses the value of an UI element) are still quite annoying to work with and require a lot of boilerplate code because it requires wrapping it with a Rc and RefCell. None of this requires any additional effort when using a GC language like Kotlin or C#.

[–] MiddleKnight@discuss.tchncs.de 2 points 1 year ago

True, but I also find that when you are dealing with circular reference and shared object scopes a bit of extra syntax and wrapping is the least of your problems.

In this case the garbage collector handles the memory for you, but for every other complication arising from these patterns you are still on your own. Keeping track of updates, locks, non-memory resource.

[–] kartonrealista@lemmy.world 2 points 1 year ago

GTK has poor compatibility with Rust, due to it's inheritance/OOP design. Iced-rs is a neat GUI library that works well with Rust's features, you define view separately from the update loop. In the view you place widgets which send messages, and the update function listens to those and based on pattern matching the message updates the central struct when one is sent.

You can often achieve the same result in a different way if you're not married to certain features, or in this case frameworks.

[–] bino@lemmy.ml 2 points 1 year ago

I would at least disagree on the browser side, look at dioxus-liveview. There is no need for js anymore 😉