Originally posted by uid313
Announcement
Collapse
No announcement yet.
Google Reaffirms Commitment To Kotlin Programming Language For Android
Collapse
X
-
- Likes 1
-
Originally posted by bug77This will be fixed in a few years. As Java gains AoT compilation capability, I'm pretty sure Google will start compiling apps on the server side and only push the resulting binaries to your phone.
Originally posted by bug77In the grand scheme of things, dependencies are the plague of everything that's not compiled down to executable code, be it Java, Kotlin, C#, Python or JavaScript (*cough*node*cough*).
- Likes 2
Leave a comment:
-
Originally posted by bug77 View Post
This will be fixed in a few years. As Java gains AoT compilation capability, I'm pretty sure Google will start compiling apps on the server side and only push the resulting binaries to your phone.
In the grand scheme of things, dependencies are the plague of everything that's not compiled down to executable code, be it Java, Kotlin, C#, Python or JavaScript (*cough*node*cough*).
Keep dependencies fine-grained, developers will complain there's too many of them; lump dependencies together, developers will complain about bloat. This used to be minor annoyance, but in the age of the smartphone and the microservices, it starts to weigh against these languages. (Don't get me wrong, they're all still viable, just a tad harder to sell in said contexts.)
That said, people don't understand the advantages of bloated applications (increased productivity while maintaining backwards compatibility). Imagine being able to run your favorite legacy GTK+ or QT based application without having any build or runtime issues.. I know I'd have crazy old beryl or superkarambas themes all over my screen. Most apps isn't expected to last very long since we have lost the ability to plan for the future and break backwards compatibility to reduce bloat (amongst other things). Simply base all our short term plans on market reaction and if it works out try to make your bloated framework or language last as long as it can possibly can. In this regard to bloated apps are the best fit for the market demands.
In all honesty related to the reason above I prefer robust native apps over feature rich, modern UX. Like discord vs IRC. I'm simply stating that I'm the minority... by far.
- Likes 4
Leave a comment:
-
Originally posted by bug77 View Post
Yes, Kotlin fixes many Java shortcomings. But man, is Kotlin code an eye sore to read... I mean, if the last argument of a method is a lambda expression, you can write it outside of the function call's parantheses. Why?
- Likes 2
Leave a comment:
-
Originally posted by bug77 View Post
This will be fixed in a few years. As Java gains AoT compilation capability, I'm pretty sure Google will start compiling apps on the server side and only push the resulting binaries to your phone.
- Likes 2
Leave a comment:
-
Originally posted by starshipeleven View PostI think that's hardly a language issue.
In the grand scheme of things, dependencies are the plague of everything that's not compiled down to executable code, be it Java, Kotlin, C#, Python or JavaScript (*cough*node*cough*). Keep dependencies fine-grained, developers will complain there's too many of them; lump dependencies together, developers will complain about bloat. This used to be minor annoyance, but in the age of the smartphone and the microservices, it starts to weigh against these languages. (Don't get me wrong, they're all still viable, just a tad harder to sell in said contexts.)
- Likes 5
Leave a comment:
-
Originally posted by tildearrow View PostHowever, it adds a ton of libraries.
- Likes 3
Leave a comment:
-
Originally posted by uid313 View PostKotlin is developed by JetBrains, not by Google.
Kotlin on Android is quite nice, partly due because Java is so horrible. Especially the outdated Java that is available on Android. No getter/setters, lambdas, type interference, etc.
Kotlin is a bit weird, for example there is no static classes/methods/properties instead there is the concept of "companion objects". It is quite nice that method arguments cannot be null unless explicitly declared as nullable, just as in TypeScript.
Also with Kotlin on Android you can reference widgets inside your views directly as if they were variables, instead of having to call the findView() method.
- Likes 4
Leave a comment:
-
Kotlin is developed by JetBrains, not by Google.
Kotlin on Android is quite nice, partly due because Java is so horrible. Especially the outdated Java that is available on Android. No getter/setters, lambdas, type interference, etc.
Kotlin is a bit weird, for example there is no static classes/methods/properties instead there is the concept of "companion objects". It is quite nice that method arguments cannot be null unless explicitly declared as nullable, just as in TypeScript.
Also with Kotlin on Android you can reference widgets inside your views directly as if they were variables, instead of having to call the findView() method.
- Likes 3
Leave a comment:
Leave a comment: