Yeah that would be great but i am not sure if that release includes the logging of HTTPClient, could you try it from latest build?
testAccount
That's already been fixed, and will be part of 0.0.51
My first attempt, is making a Kotlin multiplatform backwards compatible Lemmy API client. I'll see how it plays out.
Test missing comment please ignore
Alright we will be dropping this feature until we make a proper swipe to exit
Did you try logging in again with that account?
If it keeps happening after that what instance and what account is it?
The full sentence is This account (%s) is being verified
It's verifying that everything is correct, acc not banned, JWT works, instance alive, ...
It only shows that, if you are attempting something that causes it to be verified while already verifiying that account.
Nbd, should ve resolved itself in a few seconds
Can you also test if the problem is still fixed with this build and that the flick to exit works in the ImageViewer
https://github.com/dessalines/jerboa/files/12618555/fix_zooming_jerboa_debug.zip
np
Can you also test if the problem is still fixed with this build and that the flick to exit works in the ImageViewer
https://github.com/dessalines/jerboa/files/12618555/fix_zooming_jerboa_debug.zip
Kotlin is now preffered over Java by Google
https://developer.android.com/kotlin/first
You can still build latest apps using Java and traditional view system. There is still insurmountable of Java apps out there easily eclipsing Kotlin apps.
I prefer Kotlin because the language is so much nicer to write in. Also because the future is moving in this direction.
You can read this GTP summary on why Kotlin over Java. Or find some other dozen articles
::: spoiler summary
Kotlin has become increasingly popular for Android app development for several reasons:
-
Conciseness: Kotlin code is often more concise than equivalent Java code. It reduces boilerplate code, making development faster and less error-prone.
-
Null Safety: Kotlin's type system helps prevent null pointer exceptions, a common issue in Java. This improves app stability and reduces crashes.
-
Interoperability: Kotlin is fully interoperable with Java. You can use Java libraries in Kotlin projects and vice versa, making it easy to transition from Java to Kotlin.
-
Functional Programming: Kotlin supports functional programming constructs, which can lead to more elegant and maintainable code, especially for complex operations.
-
Extension Functions: Kotlin allows you to add new functions to existing classes without modifying their source code. This is useful for enhancing existing Android APIs.
-
Coroutines: Kotlin offers native support for asynchronous programming using coroutines. This simplifies managing background tasks, making your apps more responsive.
-
Default Arguments and Named Parameters: Kotlin allows you to specify default values for function parameters and use named parameters, enhancing code readability.
-
Smart Casts: Kotlin's type system automatically casts types when certain conditions are met, reducing the need for explicit casting in code.
-
Data Classes: Kotlin's data classes simplify the creation of classes meant primarily for storing data, reducing the amount of boilerplate code.
-
Great Tooling: Kotlin is well-supported by Android Studio and offers excellent tooling for Android app development.
While Kotlin offers many advantages, it's essential to consider your team's familiarity with the language and any existing Java codebases. Transitioning from Java to Kotlin can take some time, but many developers find it worthwhile for the benefits it brings to Android app development.
:::
Kotlin doesn't really offer a performance benefit over Java. It's negligible. It's mostly the enchanced type safety.
Kotlin being a requirement really depends on job ur applying for. There is still full Java teams. But imo more are switching to Kotlin. Or taking sorta hybrid approach. Imo Kotlin is great and the only downside i have is that learning it will make you feel annoyed when writing Bloated java again.
There is no real order of which issues get done. Everyone is welcome to contribute any feature/fix they find important.
I just work on things I find have priority which is mostly bugs first. The next big feature is probably backwards compatible API which is a huge amount of work.
There is a issue for the creation of communities. Already but it doesn't specify exactly it. Like where do we add this in UI, do we make a fullblown screen or just a popup. Which logic for showing this creation menu. Some instances don't allow users to make them. etc
Can you tell me what broke?