Not only should it tie into the existing account management API's, but I can't figure out why they're offering their own push notification API when Android has one built in!!
We've heard from a lot of people who weren't happy with C2DM. We think our push API is easier to set up and use. It's also compatible with pre-2.2 Android and with Android devices that don't have an attached Google account. You can also can send push notifications to both iOS and Android with one API call. That said, if C2DM works for you there's nothing wrong with using it directly.
As a user, I'd certainly prefer for apps that I download to use the built in system functionality (like C2DM). One of the advantages of C2DM is a standard listener that used by all apps, rather than have multiple listeners (each potentially causing battery life impact). If the C2DM API is hard to use, it makes a hell of a lot more sense to write a helper wrapper around it, rather than add another listener.
No idea why you're getting downvoted. No application that uses their own push technology is as nice to my battery as C2DM is. Facebook and Twitter can't even get push notifications right, though Google refuses to put Google Voice through the push/sync that Gmail/Calendar/Contacts have. It makes no sense to me. It's there, it's easy to use, it's really battery friendly...
It seems rather inaccurate to claim that focus-follows-mouse is "standard in Unix".
Correct me if I'm wrong, but focus-follows-mouse hasn't been the standard in Unix for quite some time. I don't think it's ever been the default in Gnome or KDE. Is it the default on anything that isn't antiquated and/or super-niche (like FVWM or TWM, etc.)?
Hey... If you want to be secure that what you need to do. The keys must not be easily accessible.
Anyway application which need to be secure are not the one you also would like to be restarted automatically or unattended: automatically restart can in many cases just make situation worse (i.e., data corruption)
You can always pay big bucks and use Oracle Database with Transparent Data Encryption: in that case, you need to enter password to open the wallet only on startup of a database.
We're required to have our sensitive data on an encrypted volume by a client (a major financial firm). Sometimes, calling the 24/7 techs to enter a passphrase is a perfectly appropriate solution, especially if you have enough capacity to let a server or two wait until the morning.
I'll certainly use circles if enough of my friends, family, coworkers, etc. start using Google+.
If Facebook had that feature, I'd be using it frequently to post geeky technical stuff to my work friends without boring my non-tech relatives, posting pictures of my kids to my relatives and close friends without boring my work friends, posting politically charged stuff to only those friends I know are on the same side of the political fence, and posting about my side business without my boss and my coworkers being able to read it! :-)
As it stands now though, most of the people I know are on Facebook, relatively few are on Google+ (yet at least), and I just end up occasionally posting fairly bland, watered down stuff that's unlikely to bother anyone, etc.
Circles, Huddles, Hangouts: Those all seem pretty different from Facebook to me. The only part of + that seems similar to Facebook is the interface of streams (which admittedly, is very similar.)
I tend to think that the similarity of 'Streams' is mainly due to the fact that that is what a social information feed looks like. It's kinda of like saying "Those word processors all copying each other with their large text areas and blinking cursors and menus" That's just because that is what works for a word processor, as the 'Stream' feed works for social updates. Just my thoughts anyhow.
I'm not sure this was obvious until Friendfeed became so popular that Facebook acquired and integrated them into their redesign in 2009. It seems like a pretty recent innovation to me.
The current 'mature' design may have been somewhat recent but that's the general distillation process of software evolution. I think in general all successful software products of similar intent migrate towards a fairly common UI layout which works best for interacting with that type of data. Not too often we see paradigm shifts in software UI's for established tasks.
Most Android apps (developed with the Android SDK) are Dalvik byte code, not native ARM code, so they should run just fine.
Apps that use native code (the developed with the NDK) probably won't work. A lot of games use at least some native code in order to leverage existing non-java libraries or code bases(the Box2d physics library for example).
It blows my mind that anyone in the startup community would automatically assume taxes = bad. Startups benefit immensely from tax funded services.
As an example, you can complain all you want about specific laws and their enforcement,but nothing remotely resembling Silicon Valley could exist without the stable legal environment provided by the tax payer funded court system and law enforcement system. Not to mention the role tax payer funding played in the initial development of the Internet, the benefit US startups get from the interstate highway system, local fire departments, etc.
Have you looked at using "git gui" instead? It seems to be a more stable, reliable, and supported tool than egit. It lacks direct Eclipse integration of course, but in practice I've never found that to be a problem.
Maybe I was misunderstanding, but I assumed the parent comment was wanting to be able to easily select individual changes from his re-factoring for committing. Git GUI is great for that. I'm not aware of any additional "refactoring" related functionality that eGit offers above and beyond that.
I used to assume the same thing (I love the buttons on my N1!) until I used a Gingerbread tablet for awhile.
The software "buttons" on a Gingerbread tablet are pretty much identical to the capacitive buttons on most Android phones, but they have the advantage of rotating with the tablet. Turn it any direction: sideways, upside down, etc. and all the buttons are still in the same relative location. It's nice actually.
