Kotlin vs. Java – An Android Developer's First Impressions
1–10 of 23 posts
Re: Kotlin vs. Java – An Android Developer's First Impressions
#2Re: Kotlin vs. Java – An Android Developer's First Impressions
#3Re: Kotlin vs. Java – An Android Developer's First Impressions
#4Perhaps a little off-topic, but can anyone share their experience with using Kotlin to build a non-trivial web app and what their stack was?
Re: Kotlin vs. Java – An Android Developer's First Impressions
#5Off-topic but is anyone else unable to scroll on this page?
Whenever you have such a complaint - and choose to make it public - please include more details. What system, what browser, add-ons (adblocker) at least.
EDIT: Downvotes? For answering the question truthfully? It does work for me. The question was (is) "is anyone else unable to scroll on this page?" -- and I have no problem scrolling. I answered the question! The question was NOT "do you think the page is designed badly". If that is what was meant, that is why I said "needs more details". All the person asked was about "being able to scroll"! And the design issue does not prevent it. I answered the question that was actually asked! I assumed, and still do, that the person isn't able to scroll at all.
Re: Kotlin vs. Java – An Android Developer's First Impressions
#6I mean, ignoring functional stuff which is in Java 8 but not on Android because Android is still(?) on Java 7, that's all I'm really seeing here.
Re: Kotlin vs. Java – An Android Developer's First Impressions
#7If you have developed in Swift (and probably other languages), Kotlin will feel very similar, the only thing you need to do is learn the native API's, but logic/model code is so similar you can just copy paste from swift->kotlin and vice versa and just fix 2-3 syntax issues
Re: Kotlin vs. Java – An Android Developer's First Impressions
#8Not to sound disparaging, but could this basically be summed up as "Kotlin is the syntactic sugar version of Java"? I mean, ignoring functional stuff which is in Java 8 but not on Android because Android is still(?) on Java 7, that's all I'm really seeing here.
After porting our code base to Kotlin we found it provides more benefits over Java than just being less typing / "syntactic sugar". To name a few:
- First class functional support (streams feel clunky in comparison).
- Extension functions [1].
- Nullable types (compile-time null checking).
- Less verbose as types declarations are optional in many situations.
- Great interop & tooling from JetBrains makes a slow transition from Java -> Kotlin pretty seamless.
[0] https://developer.android.com/studio/preview/features/java8-...Re: Kotlin vs. Java – An Android Developer's First Impressions
#9Not to sound disparaging, but could this basically be summed up as "Kotlin is the syntactic sugar version of Java"? I mean, ignoring functional stuff which is in Java 8 but not on Android because Android is still(?) on Java 7, that's all I'm really seeing here.
Default and static interface methods
Lambda expressions
Repeatable annotations
Method References
Type AnnotationsRe: Kotlin vs. Java – An Android Developer's First Impressions
#10Off-topic but is anyone else unable to scroll on this page?
Works for me. Whenever you have such a complaint - and choose to make it public - please include more details. What system, what browser, add-ons (adblocker) at least. EDIT: Downvotes? For answering the question truthfully? It does work for me. The question was (is) "is anyone else unable to scroll on this page?" -- and I have no problem scrolling. I answered the question! The question was NOT "do you think the page…
The scrollbar is also hidden behind the top banner in some way, which suggests it's doing something non standard.
Why do people want to fiddle with the most basic UI/X idiom on the net?