makeramen

Have you considered RxJava?

Yeah but it's already namespaced differently so package name shouldn't conflict. But now that I think about it more, consistent versioning for the 3rd party dev across multiple OS versions is pretty important.

That's true, I totally agree with you at its irony in hindsight. I guess I'm a bit blinded at having worked on Android apps for a while and using this lib way too often.

Not entirely sure how this made front page, but it is a super handy lib.

I don't understand why Android includes this lib in their source but makes it internal so you have to provide your own copy if you want to use it in your app: https://android.googlesource.com/platform/external/libphonen...

> The My KNOX console provides password reset functionality, thus removing the need for password hints.

Wait, doesn't that mean Samsung has a way to decrypt your data without the original password then? (Though I'm not familiar with MyKNOX so I'm not sure if that's what they're promising at all)

This is the first time they're offering a peek into a pre-release of their OS, ever. Apple has done multiple times with a track record of auto-updates, so yes, that can be expected of Apple, and Apple only.

Google never promised updates, never promised stability, it's not a beta, it's not a GM, it's not even alpha. It's simply a preview. You get what they say you get. Don't set iOS's standards on Android, they're completely different products, with completely different cultures, release cycles, everything.

There are a lot of products, Google and otherwise, that go straight to release without any prereleases. If anything Android has has a very strict record of that, so I think your expectations of much more from them on such a large release like L is simply unfounded.

And C# can't (directly) run on anything not built by Microsoft. For those of us focused on shipping products to cross platform users, there are handfuls of languages better than C# in that regard. There are things every language does poorly and well, but you also don't see us making whycsharpsucks websites because we're probably too busy building things.

I just don't see the need for this kind of negativity. If a language wasn't designed for a certain way of using annotations (or any feature), maybe another method should be tried to get similar results. It may not be ideal and may not fit the paradigms of what you're used to, but it's a completely different language for heaven's sake.

It's like asking why a Honda Accord isn't faster than a Lamborghini... But at least the Accord holds 4 people and has useable trunk space. They're built for different needs, nobody expects an accord to race well, and nobody expects a lambo to be good for soccer moms and off-roading. So why the hate?

I use Parceler (https://github.com/johncarl81/parceler) with gson. So gson for network data, then parceler for passing parcels around between activities/fragments.

From my conversations with iOS developers, those libraries don't come close to the robustness and simplicity of equivalent java/android libraries like retrofit, gson/jackson, coupled with RxJava... Etc.

I do think a large part of that is due to lack of generics that allow the code to recursively deserialize nested classes and collections without any extra boilerplate other than the class definitions.

I know for a fact that mantle just can't do that with obj c in its current form.

FWIW, Clinkle was housed in Mountain View for quite a while. While I generally agree with you on the distinction between established players vs startups, I don't think the geographic classification is clear cut as you make it.

Just because the founders put effort into something doesn't make it ethically good. The advertised use is still messaging and communication, and I'm sure if they open it up to developers there will only be more distractions like flappy birds on a car. The point is a powerful technology with smart people and good intentions behind it can always result in poor unintended consequences. In this case I can see a lot more potential consequences than advantages.

I think they're trying to copy Google+'s "Photos" app which takes over the gallery while offering background upload in the same app.

Although on Android with Google+ it's bundled in the same apk, just 2 separate Launcher icons.

As an Android Developer, I would urge aspiring mobile developers to think about it this way: In which market is there more demand for developers?

I know so many companies that need good android devs and can't find any because nobody has the experience. From my anecdotal experience, the demand for Android Developers is much higher than iOS (relative to the supply) at the moment.

The experience of the developers is also a huge factor.

Actually "Eclipse is the default" is probably going to be false very soon. Every mid to senior level Android developer I know has migrated to Android Studio for months already. The advantages of Gradle and Studio are very apparent almost immediately.

I thought the Nexus 4 had been unavailable for a while now?

control + shift + eject/power.

But really, I'd prefer this to be an app on my phone instead of a keychain. I usually walk away from my computer with my phone but I'll leave my keys on my desk because they're more uncomfortable in my pocket.

Although I'm pretty sure doing that in android still uses your mobile number and cell network to make the connection, not the WiFi or data connection. So it's still not true VoIP/WiFi-calling like it is on the iOS version of hangouts.

I'd liken this to the "washing machine effect" that Hans Rosling explaned in his TED talk [1]. He essentially made the case that the washing machine made a huge difference in the history of the world so parents could spend more time with their kids (among other things) instead of many hours a week just washing clothes. I would say Google Shopping Express has a similar effect for shopping trips where the time spent greatly affects the amount of things an individual can accomplish in a day.

[1] http://www.youtube.com/watch?v=BZoKfap4g4w

This could be huge. Even if they just take the route of updating the most popular phones to the latest versions of Android, bypassing the slow manufacturer+carrier update cycle, they could easily have a platform if they can get the adoption.

Make an easy "switch to CyanogenMod" installer for the top handsets, and provide your own OTA updates faster than the actual device manufacturer and you could have quite the platform. Plus Google will love you since you're keeping more of their devices up-to-date, essentially fighting the fragmentation problem for them.

One thing Google will never do is firmware/bootloader level programming to specific devices, and actually writing the code that lets you update your carrier/manufacturer controlled device to the latest version of Android.

CyanogenMod could effectively help more users get the latest version of Android faster than manufacturers and carriers would, and continually do so with their own software OTA cycles and suddenly have a platform of Android on top of the major devices regardless of manufacturer/carrier.

How is the Linux compatibility with transforming/dock computers like this? This would make one hell of a portable dev machine.

HN duplicate filter not working? https://news.ycombinator.com/item?id=6162813 is #1 front page right now.

I don't remember what other sites they were, but I've done this a few times for identity verification, seems like there's a central provider somewhere that does the same thing for different businesses

Correction: "lacking in any realtime capabilities" should read "offline capabilities". And by that I mean offline without manually managing cache.

Also by 2-way sync I mean 2-way cache sync. Firebase is actually really good with 2-way sync, but without cache/offline (yet) it's kind of a dealbreaker for me.

As someone who has been playing around with Parse and Firebase SDKs (on Android), this seems to be the first one that offers full 2-way sync. I haven't actually used it yet but it seems that way due to the presence of conflict resolution [1]. I'm personally really excited about that for mobile side-projects and MVPs.

Parse has an offline cache, that only caches query results and not actual objects. So any local saves/updates are not reflected until you get network access again, unless you manually implement your own cache.

Firebase is better at handling realtime changes, but is lacking in any realtime capabilities at the moment. Also Firebase's mobile authentication SDK still isn't released yet so no way to handle users yet either.

[1]: https://www.dropbox.com/developers/datastore/tutorial/androi...

Please link to github status: https://status.github.com/ which I assume is run on separate servers and actually provides useful information on the current status.

This is really interesting. I wonder if the existing California Highway Patrol practice of swerving around the highway[1] to slow down traffic can be used to create these "anti-traffic" gaps during rush hour?

[1] http://articles.latimes.com/1996-08-12/local/me-33464_1_traf...

Someone should mark this (2011).

South provides stable and mature migrations for schema changes [1]

Custom Auth models are now available in Django 1.5 [2]

The templating language definitely needs some work, but it's slowly getting better. I'd prefer them drop in Jinja2 but that's just me.

[1] http://south.readthedocs.org/en/latest/

[2] https://docs.djangoproject.com/en/1.5/topics/auth/customizin...

Having a bitbucket mirror isn't a bad idea. They have free private repos for up to 5 users, so if you just have an admin and the deploy user on there you can get redundancy for "free". Just have to keep it in sync, but that shouldn't be too hard with DVCS and everyone having a local copy.