Android, evolvability and Comcast

Re:Android, evolvability and Comcast by diyseguy on Sunday April 23, 2017 @01:23PM (#14179144)

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)

[ Parent | on HN ]

Re:Android, evolvability and Comcast by CyberDildonics on Sunday April 23, 2017 @03:57PM (#14180131)

> Why didn't they use Python

Are you seriously suggesting using 50x the processing power as a native program on a mobile phone?

[ Parent | on HN ]

Re:Android, evolvability and Comcast by lostmsu on Monday April 24, 2017 @02:18AM (#14182285)

Did he even ever develop a single complex UI app (or any app actually) in Python?

[ Parent | on HN ]

Re:Android, evolvability and Comcast by diyseguy on Monday April 24, 2017 @02:27PM (#14186713)

he did :P

[ Parent | on HN ]

Re:Android, evolvability and Comcast by yjftsjthsd-h on Sunday April 23, 2017 @03:21PM (#14179908)

Probably historical reasons; when Android was created, was Python good enough? Particularly on underpowered processors with tight power requirements?

[ Parent | on HN ]

Re:Android, evolvability and Comcast by diyseguy on Monday April 24, 2017 @02:25PM (#14186700)

At the time Google started promoting Android OS, Google was well known to use primarily Python internally. So I was very shocked and discouraged by their choice of Java. I assume it was to reach the widest developer audience at the time. Maybe a case can be made for using Java otherwise, but Java is my least favorite language due to it's excessive verbosity and other pointlessly fussy restrictions.

[ Parent | on HN ]

Re:Android, evolvability and Comcast by yjftsjthsd-h on Monday April 24, 2017 @03:48PM (#14187483)

Android was not started by Google; I presume when they bought Android Java was already entrenched

[ Parent | on HN ]