Google I/O 2014 - Android fireside chat

Google for Developers · 18K views · 2014 · 48:32

Open on YouTube

Software architecture & designTech company stories & documentariesinterviewdated

Why Hacker News recommends it

HN cites specific moments, such as the team's stance that Java is the official language and its answers on Scala and permission-revoking.

What it is

A Google I/O 2014 fireside chat in which members of the Android platform team answer questions about why the platform works the way it does. It is moderated by developer advocate Reto Meier.

Recommended by 0 HN commenters across 0 different months, 2014 to 2016.

What Hacker News said

Cites pjmlp · 2014-09 · on “Official Go support”

Yes, [this video] - Java is the official language, that is what the team has invested into - You can use the NDK for your favorite language, but beware that you are required to use JNI anyway for Android APIs - Not possible to do any comment regarding Java 8 support. - Only use Scala for business logic, no tooling support plans

Cites shadowmint · 2014-12 · on “Android: I don't need your permission”

This reminds me of the recent fireside android chat at I/O where someone said something like "I need to be prepared for although I got the permission, it might not be there". ...and they said "We work on the Play Store, and uh... that's not something we have any idea about" "No, I think he's talking about the ROM's that let you take a permission away. Wanna talk about AppOps?" Everyone looks awkward. 'No'. Ok... let's quickly talk about something else instead. (watch it here. Fun times. [this video] )

Cites aphexairlines · 2016-05 · on “Android platform engineer on application architecture”

26min into the 2014 Google I/O Android fireside chat: [this video] Q: So I was wondering if you guys at any point considered the support -- the official support -- of the Scala programming language. I'm asking this question especially now that we all saw that Apple released Swift after 4 years of work. And I think that Swift allows for things for iOS developers that we can't do in Java with the Android SDK. So my question was: have you ever thought about it before -- the release of Swift? Have you thought about it after that? Is there any plan? Android answer 1: Well, so, I like Cocoa, but Objective-C is based on C, which is 40 years old, so I think Apple sort of had to, like, update it a bit. Um