Kt. Academy’s Post

It took me many days of experiments, but I finally finished what is likely one of the most important articles in my career. Welcome "How many threads your network client uses?". What is it about? After discovering that Retrofit wastes threads for network calls, I made experiments to check different popular network clients used in Kotlin to establish how they use threads. On the way, I discovered some of their problems.

In Android development, mastering memory management is crucial for building high-quality and efficient applications. One of the fundamental concepts to grasp is the interplay between memory leaks and garbage collection. checkout my new blog about this from the learn android from basic to advance series https://lnkd.in/dU-MBamS #android #androidappdevelopment #mobileappdevelopement #memoryleak #garbagecollection #blog #hashnode

Picasso is now being deprecated as announced by the legend Jake Wharton! Picasso was a benchmark for what an Image Loading Library should be and also helped so many of us, learn about Bitmap pooling, image downloading, caching, RAM management etc And most importantly, helped tackle the system design question "Design an Image Loading Library" Jokes Aside, Coil is a brilliant alternative which is purely Kotlin and coroutines. Do take a look if you're migrating https://lnkd.in/dN5GyJFY

It took me many days of experiments, but I finally finished what is likely one of the most important articles in my career. Welcome "How many threads your network client uses?". What is it about? After discovering that Retrofit wastes threads for network calls, I made experiments to check different popular network clients used in Kotlin to establish how they use threads. On the way, I discovered some of their problems.

Android's use of safe-by-design principles drives our adoption of memory-safe languages like Rust, making exploitation of the OS increasingly difficult with every release. To provide a secure foundation, we’re extending hardening and the use of memory-safe languages to low-level firmware (including in Trusty apps). In this blog post, we'll show you how to gradually introduce Rust into your existing firmware, prioritizing new code and the most security-critical code. You'll see how easy it is to boost security with drop-in Rust replacements, and we'll even demonstrate how the Rust toolchain can handle specialized bare-metal targets. Drop-in Rust replacements for C code are not a novel idea and have been used in other cases, such as librsvg’s adoption of Rust which involved replacing C functions with Rust functions in-place. We seek to demonstrate that this approach is viable for firmware, providing a path to memory-safety in an efficient and effective manner.

Here I go again.🚀🚀 It's time to publish the 4th part of the SOLID with Kotlin article. Now let's talk about the Interface Segregation Principle and the importance of creating specific interfaces, leaving aside those interfaces with different methods that it doesn't make sense for every class to implement.

Hey guys! I made a new post on Medium. This time, I will explain about threads in Node.js. The idea behind it, the misconception about this subject in this JS runtime, and a straightforward example.

What I'm asking is how I can change what will show up, when I use long press of the power button. U Check it out: https://lnkd.in/dA7mb_SG Join the conversation! #android #androidstudio #java

Understanding of memory alocation will make you rethink on the order of declaring variables

I have always believed that you should not use Jetpack Compose stringResource function for retrieving or manipulating strings. However, there is a sample from official source that does exactly that: https://lnkd.in/dxv9EKWE Method lastUpdated on line 483 that returns a String as a Composable function. In my opinion, Composable functions should emit UI and not be used to return text. I still believe that we should not be using stringResource function invocation when it comes to manipulating a String. Why not just have a pure Kotlin method that returns a string resource id in a form of an Integer and then just combine that returned result in the UI layer with stringResource invocation? Which approach do you follow and what is your opinion?