Android, evolvability and Comcast

#1

Post by awinter-py » Sun, Apr 23, 2017, 3:03 PM UTC

Android, evolvability and Comcast
abe-winter.github.io

Re: Android, evolvability and Comcast

#2

Post by mayoff » Sun, Apr 23, 2017, 4:38 PM UTC

If this post gains traction, its title will probably be changed to “Android, evolvability & comcast” since that's the title of the linked article.

So here, for posterity, is the original post title, which made me chuckle:

  If you like calling comcast you'll love android studio

Re: Android, evolvability and Comcast

#3

Post by Infinitesimus » Sun, Apr 23, 2017, 4:49 PM UTC

The Java problems the author complained about can be addressed by switching to Kotlin.

I hope Google gives Kotlin 1st class support in android studio and even pushes it as the default language as it is more pleasant to use in my experience.

Not sure single file creation of an Android app (with a user inferface) is possible/advisable though since the separation of view concerns and logic concerns can come in handy. Gradle can be confusing to a first time user but Android studio does provide a GUI for managing dependencies.

Re: Android, evolvability and Comcast

#4

Post by vikeri » Sun, Apr 23, 2017, 4:53 PM UTC

The solution is called React Native.

- Single file app: Check

- Super fast rebuild: Check

- Dynamic language (high reusability and one-liners): Check (Use ClojureScript to take this even further)

Re: Android, evolvability and Comcast

#5

Post by krzyk » Sun, Apr 23, 2017, 5:22 PM UTC

vikeri wrote: post #4

The solution is called React Native. - Single file app: Check - Super fast rebuild: Check - Dynamic language (high reusability and one-liners): Check (Use ClojureScript to take this even further)

But there is a single problem with React Native: Javascript (and all languages that come from it). It's frequently one of the most hated ones as it is loved.

Dynamic language is not necessary the best thing invented, if it were there wouldn't be any other kind of languages.

Re: Android, evolvability and Comcast

#6

Post by diyseguy » Sun, Apr 23, 2017, 5:23 PM UTC

Amen! I find Android programming excessively verbose and convoluted. I thought Google was supposed to be staffed by geniuses. The whole thing feels designed by a committee - like something Microsoft would put out. Why didn't they use Python? (Yes I've tried Kivy - meh)

Re: Android, evolvability and Comcast

#7

Post by JustSomeNobody » Sun, Apr 23, 2017, 5:45 PM UTC

vikeri wrote: post #4

The solution is called React Native. - Single file app: Check - Super fast rebuild: Check - Dynamic language (high reusability and one-liners): Check (Use ClojureScript to take this even further)

There is something seriously wrong with our industry. How can this even be suggested as a solution?

Re: Android, evolvability and Comcast

#8

Post by dingo_bat » Sun, Apr 23, 2017, 5:48 PM UTC

I never could put my finger on it till now, but this is why I found Android dev frustrating.

Re: Android, evolvability and Comcast

#9

Post by guelo » Sun, Apr 23, 2017, 5:50 PM UTC

I'm not saying Android development or Java are that great but this guy spent two weeks on it. That's not enough time to get a feel for the environment. It doesn't matter what the language is, if you drop a developer into a completely unfamiliar one they will feel awkward annoyed and lost for at least a couple months.

Re: Android, evolvability and Comcast

#10

Post by ryukafalz » Sun, Apr 23, 2017, 5:59 PM UTC

Speaking of those terms and conditions, I was really surprised to see this in there:

>You may not use this SDK to develop applications for other platforms (including non-compatible implementations of Android) or to develop another SDK. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose.

Older versions of Android Studio were under the Apache License 2.0, but they seem to have changed that sometime in 2015.