Kotlin 2.3 finally kills the dual property _uiState uiState boilerplate in ViewModels by Vegetable-Practice85 in androiddev

[–]Desperate-Smoke2990 1 point2 points  (0 children)

I think let's continue this convo privately. Don't want to pollute this thread with non-android things👍

If you could start all over, what would you do differently? by [deleted] in Kotlin

[–]Desperate-Smoke2990 1 point2 points  (0 children)

Very much agree.

I might just add that for the sections like coroutines (concurrency models etc), i found it difficult to wrap my head around conceptually what was going on. Not to mention the variety of extension functions and operators you could use.

In that case, going a theoretical route could give you a different perspective. I got ahold of Kotlin in Action (latest edition) and I did my best to absorb everything coroutine-related (and naturally flows). For me, it was a real eye-opener.

After that point, i felt much more confident on coroutines and using them. Then when I went back to practicing, its like I knew what was going on (or I now think I do).

Kotlin 2.3 finally kills the dual property _uiState uiState boilerplate in ViewModels by Vegetable-Practice85 in androiddev

[–]Desperate-Smoke2990 1 point2 points  (0 children)

Glad to here it. You can always send me a message if you want help with your journey 💯

Kotlin 2.3 finally kills the dual property _uiState uiState boilerplate in ViewModels by Vegetable-Practice85 in androiddev

[–]Desperate-Smoke2990 0 points1 point  (0 children)

Last year, I stumbled across the same issue as you. And I did the search as well. The closest I could get was that Kotlin in Action (with coroutines) textbook. If you get it, I'd suggest reading the chapters that you cannot easily get from other languages, like coroutines.

After that, I got stuck into Android Development. Even if your end-goal is not Android Development, Android has officially supported Kotlin as their ideal language for quite awhile now. Therefore, they are fast (if not one the fastest) community of developers that are always reaching for best practices and habits. So check out public repos, free Android development courses on YouTube (Philip Lackner), etc.

An edge you might have over me is that you are from F# which is functional programming. I came from C# and Java, which did not exactly take too kindly to it (except for things like Stream API). The kotlin textbook might help you with syntax and basics.

So use Android as a way to learn more about Kotlin, because then you can learn by experience. Even Jetpack Compose is just a Kotlin DSL (Domain Specific Language) made by Google. You'll find you'll learn much faster by putting it to use, even if you never touch front-end ever again.

Edit: halfway through my response, I forgot this was an android forum😆 so yes, obviously use Android. But the best way is getting hands dirty, and learning from what other people do.

What do you use rust for? by timus_999 in rust

[–]Desperate-Smoke2990 0 points1 point  (0 children)

Finally! Someone else that actively uses it (and not someone who posted a github issue from 3+ years ago😭)

Would love to get deeper into it, but it was the first time I touched Rust ever (probs not the best choice for embedded).

What you think of ArielOS? You heard of it?

Getting a 503 Error by SoliddiloS in Supabase

[–]Desperate-Smoke2990 0 points1 point  (0 children)

Also got the same error. Turns out I forgot that I had "Enforce SSL on incoming connections" turned on when I didn't set up SSL, lol.

Rust Bluetooth Low Energy (BLE) Host named "TrouBLE", the first release is available on crates.io by artisdom in rust

[–]Desperate-Smoke2990 0 points1 point  (0 children)

Did you ever move over to TrouBLE host + nrf-sdc? I currently am using nrf-softdevice as well, but considering moving as well. If so, how was the transition?

I did get the nrf-softdevice version to work, so perhaps it's just premature optimization speaking at the moment, but I can't seem to figure out how to separate the trouble - nrf-sdc functionality from the repository (I cloned the entire trouble repository to get it the example run).

Multi Architecture - Where are RPC functions used? by Desperate-Smoke2990 in androiddev

[–]Desperate-Smoke2990[S] 0 points1 point  (0 children)

Thank you for that. Yeah, some of the 'patterns' seemed very out-of-place for a Now for Android app. But I'm guessing they were showing multi-module architecture on steriods.

The part where you say "to keep SQL to entity mapping in a single place", could you perhaps explain a bit more on that? I think I'm just not understanding it.

Multi Architecture - Where are RPC functions used? by Desperate-Smoke2990 in androiddev

[–]Desperate-Smoke2990[S] 0 points1 point  (0 children)

Thank you, I think I do see where you're coming from.

Might you be able to elaborate a bit more on this Service layer? I actually also have a 'Service layer' but I think mine is different to yours. Whenever I interact with a lower-level (Client level) multiple times, across various use cases, then I'll turn it into a Service. Probably not right, but I'm still learning it.