News for hackers. Stuff that matters.
Re:Go support for Android by fidotron on Friday June 20, 2014 @10:25PM (#7923913)
The problem with Android isn't Java though, it's the Android API being an inconsistent hacked together in a hurry trainwreck. Everything they've added since 3.x has been an enormous improvement, but they never shook off the baggage of the initial push to release.
Re:Go support for Android by rdtsc on Friday June 20, 2014 @11:11PM (#7924018)
Funny I had the exact opposite impression after using Java years ago. I felt like Android's API redeemed Java in my eyes a bit. I never liked Java much but the emulator, the debugger, a documented API, lots of example, developer blogs all made it very easy to get started and I create a rather complicated app pretty quickly.

Looking back I wouldn't mind developing on Android again but I wouldn't want to necessarily do anything with Java by itself.

Re:Go support for Android by jm547ster on Saturday June 21, 2014 @01:10AM (#7924269)
Have to agree, I thoroughly despised Java until I started developing for Android, it suited the Application Framework and made the language fun, developing fully functional apps with ease and speed.
Re:Go support for Android by bennyg on Saturday June 21, 2014 @12:39AM (#7924219)
Tell me about it. I'm constantly using the autocomplete to look through all options to complete a method when it should be consistent with other similar things. For instance, you set OnClickListeners but you add TextChangeListeners. This is just a simple example, and yeah it's a small thing, but it's the damn mental baggage of not relying on my brain's quick search to find similar things and having to spend the extra time that really wears on you after hours of it.

The level of hackery even drips down to their own documentation and code examples. There is a line in an old example for a TabPager I believe that said "It relies on a trick." How is this acceptable API writing and role-modeling from Google?

Re:Go support for Android by myko on Friday June 20, 2014 @10:33PM (#7923931)
Fair enough. Even some of the newer APIs feel slopped together to be honest. Android development does feel like a constant battle with framework bugs.
Re:Go support for Android by shakethemonkey on Saturday June 21, 2014 @02:07AM (#7924325)
All android APIs tend to have a large number of methods, but there will be absurd omissions. Example, the WebView has no way to return its HTML contents. So it's difficult to implement your own caching mechanism. Or an even more absurd example, the android YouTube player has no .stop() -- it is simply inconceivable that a media player lacks a way to stop a video, but there it is.
Re:Go support for Android by Shish2k on Saturday June 21, 2014 @03:56AM (#7924453)
Back when I was writing a client for a REST website, the default HTTP library lacked POST. The recommendation was that every app which wanted to POST should bundle the ~2MB apache HTTP library, which seemed a little painful given that other than that, our app was ~50KB :(
Re:Go support for Android by Ironlink on Saturday June 21, 2014 @06:02AM (#7924609)
> Example, the WebView has no way to return its HTML contents. So it's difficult to implement your own caching mechanism.

That's a feature to me. Respect my Cache-Control headers!

Re:Go support for Android by fit2rule on Sunday June 22, 2014 @05:19AM (#7927339)
Look at it like this: if you need an IDE to get code written, things have gone off the rails. Most Android developers would be absolutely useless without code completion ..